Hi all,
Apologies if this is a simple question, but I cannot get graceful exit to work. Below is the command I use to start the node:
sudo docker run -d --restart always --stop-timeout 300 -p 28967:28967/tcp -p 28967:28967/udp -p 14002:14002 -e WALLET="REDACTED" -e EMAIL="REDACTED" -e ADDRESS="REDACTED" -e STORAGE="900GB" --log-opt max-size=50m --log-opt max-file=10 --mount type=bind,source=/home/admin/storj,destination=/app/identity --mount type=bind,source=/mnt/storj/storagenode,destination=/app/config --name storagenode storjlabs/storagenode:latest --operator.wallet-features=zksync-era
but when I enter the following command:
sudo docker exec -it storagenode /app/bin/storagenode exit-satellite --config-dir /app/config
I get the following error:
OCI runtime exec failed: exec failed: unable to start container process: exec: "/app/bin/storagenode": stat /app/bin/storagenode: no such file or directory: unknown
Thanks in advance to anyone who can help.
LrrrAc
February 11, 2025, 2:21pm
2
This is the command I used. For whatever reason the location of the file “storagenode” was different. Try that.
sudo docker exec -it storagenode /app/storagenode exit-satellite --identity-dir /app/identity
2 Likes
Thanks, that worked. Knew it would be simple!
1 Like
LrrrAc
February 11, 2025, 4:03pm
4
Took me a while to figure out, glad to save you some time.
Alexey
February 13, 2025, 8:26am
5
Hello @jonnyrider ,
Welcome to the forum!
@LrrrAc @jonnyrider
It could work only if you never updated the base image (e.g. do not have a watchtower and didn’t run docker pull storjlabs/storagenode
after setup).
The latest base image put binaries to /app/bin/
folder.
1 Like
LrrrAc
February 13, 2025, 8:33pm
6
I regularly pull new images, when was this changed? I used the /app/bin location before, i was forced to figure out the new /app location months ago.
Alexey
February 15, 2025, 3:05am
7
This is weird. The latest change is there:
committed 06:40AM - 03 Oct 24 UTC
* fixed exec issue for restricted systems
* fixed the case with the older ver… sion in storage
* fixed the case if the suggested version is not allowed yet
* unified check for a new version
* remove BINARY_DIR, change BINARY_STORE to BINARY_STORE_DIR
Change-Id: Ic5da0d1303e3f19d4e577bf9a58081b29c9208da
---------
Co-authored-by: Clement Sam <clementsam75@gmail.com>
So, I do not know how you managed to get binaries back to /app
unless you used the older base image.
LrrrAc
February 15, 2025, 4:06pm
8
I just checked and it’s app/bin again. I used that before, then had to figure out it was changed to /app/, but I guess it changed back since I last used it. Odd.
Alexey
February 16, 2025, 8:16am
9
Maybe some of your hosts have an old base image, some - the new one?
LrrrAc
February 17, 2025, 4:17pm
10
Could be, but regardless, now they match what you say they should.
1 Like