Hi fellow node operators…
I have found that one of my nodes is running in ‘snap’
How can I easily move this over to ‘apt’ ?
Anyone done this - can give me some guidance / pointers
Cheers
Hass
Hi fellow node operators…
I have found that one of my nodes is running in ‘snap’
How can I easily move this over to ‘apt’ ?
Anyone done this - can give me some guidance / pointers
Cheers
Hass
Hi @ItsHass,
If it’s working normally, you may leave it as is - this is not needed to fix what is not broken. But if you have issues, then this is should not be so hard.
docker stop -t 300 storagenode
docker rm storagenode
sudo snap remove docker
When you finish and docker will work, you can start the storagenode container with the same full docker run
command with all your parameters as before.
Please do not run the SETUP step for the existing node!
docker in snap may provide better security on the host. If its working may want to stick with it.
Hey Alexey,
what exactly does
docker stop -t 300 storagenode
do? I am always just using the stop without -t and am wondering now.
This instructs docker to wait for up to 300 seconds for the app running within the container to exit, before killing it.
The default value docker uses is way lower than that (10 seconds I believe) which may not be enough for the node software to shut down cleanly if it’s busy.
It should not be a problem, if you did not specify the grace timeout before the container will be killed, because if you used a docker run
command from the guide - it includes this grace timeout for the container.
I’m trying to use the Docker API , i think usually on port :4342 - I don’t seem to be able to do this on snap, but i’ve done this on apt docker without any issues following a guide
Do you have any knowledge of that ?
Cheers
Hass
Because docker snap is more contained and does not share kernelspace i believe you have to expose the port manually to docker.sock. I do not have experience with this, but perhaps this may help. This of course adds some exposure to your host that may bring some of the similar exposure pathways that apt docker does. It’s still probably more secure.
cheers for this - i will give it a try