search

pi-node / instructions

266 stars 190 forks source link

Docker container not running automatically on boot up thus impacting node availability #13

Open engboniface opened 4 years ago

engboniface commented 4 years ago

Some win10 pro users have to start the docker container manually every time they boot up the computer. The user manually starts by clicking the 'play' button on docker (SS below). image after pushing 'play' button. image

This means the node is not active if ever the user forgets to push the 'play' button. It's unclear how many pioneers are affected by this at the moment.

engboniface commented 4 years ago

Solution thanks to @testius:

Run the command 'docker ps -a' on command line to find out your containerID. Then run the command 'docker update --restart=always 2c7d17' where 2c7d17 is your containerID.

With this command, the docker should start automatically on boot up.

efishdew commented 4 years ago

The result of executing this command is that Docker will run automatically next time? Or can the problem be fixed completely?

engboniface commented 4 years ago

The result of executing this command is that Docker will run automatically next time? Or can the problem be fixed completely?

After running this command, the docker container starts automatically every time i restart the computer. No need for manual intervention.

efishdew commented 4 years ago

I followed the above, but it returned an error message.

Microsoft Windows [Version 10.0.18363.836] (c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ac662859fd5e ese7en/node-port-test "node index.js" 4 weeks ago Up 6 days 0.0.0.0:31400-31409->31400-31409/tcp stellar-dummy

C:\WINDOWS\system32>docker update --restart = always ac662859fd5e Error response from daemon: No such container: always Error response from daemon: invalid restart policy '='

C:\WINDOWS\system32>

efishdew commented 4 years ago

docker update --restart=always CONTAINER ID

That's the right command line. I've found the reason for my mistake.There can be no spaces before or after the = When executed correctly, the system returns my CONTAINER ID instead of an error message!

ihatejam commented 4 years ago

Solution thanks to @testius:

Run the command 'docker ps -a' on command line to find out your containerID. Then run the command 'docker update --restart=always 2c7d17' where 2c7d17 is your containerID.

With this command, the docker should start automatically on boot up.

Do not do this. The consensus container will need the ability to stop the listener container. If you have it set to auto-restart, then the consensus container will not be able to use the ports while the listener is holding onto them.

efishdew commented 4 years ago

I executed this command before entering the consensus container testing team, so my docker will start automatically. If this is wrong, how should I undo the operation.

efishdew

2020年9月2日(水) 8:53 ihatejam notifications@github.com:

Solution thanks to @testius https://github.com/testius:

Run the command 'docker ps -a' on command line to find out your containerID. Then run the command 'docker update --restart=always 2c7d17' where 2c7d17 is your containerID.

With this command, the docker should start automatically on boot up.

Do not do this. The consensus container will need the ability to stop the listener container. If you have it set to auto-restart, then the consensus container will not be able to use the ports while the listener is holding onto them.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pi-node/instructions/issues/13#issuecomment-685193281, or unsubscribe https://github.com/notifications/unsubscribe-auth/APOIRDR652M7FR2WQC54EJ3SDWCQPANCNFSM4NSSTNOQ .

ihatejam commented 4 years ago

no problem - you can disable it again with:- docker update --restart=no containerID

more info can be found in the docker documentation at https://docs.docker.com/engine/reference/run/#restart-policies---restart

efishdew commented 4 years ago

Thank you very much! I have restored the default settings. Hope the node network will run soon.

efishdew

2020年9月2日(水) 22:00 ihatejam notifications@github.com:

no problem - you can disable it again with:- docker update --restart=no containerID

more info can be found in the docker documentation at https://docs.docker.com/engine/reference/run/#restart-policies---restart

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pi-node/instructions/issues/13#issuecomment-685719150, or unsubscribe https://github.com/notifications/unsubscribe-auth/APOIRDTSCDR3A5W3B22BEQ3SDY6WDANCNFSM4NSSTNOQ .

Mogithub2020 commented 4 years ago

Hear ye, hear ye, I really need help with my Pi node. When checking for open ports, it gets stuck at "Pinging your computer", so there is no way of telling if it has pinged the computer or not. I have used different avenues to confirm that the ports are indeed open. I have also done port forwarding on my router.

Secondly, when I open the troubleshoot page on the Pi node, it tells me that the consensus container is absent and not enabled. I took a look in Docker Desktop and could only find the port test container. Is there anyway around this please?

My computer runs on widows 10 home with WSL 2 and I am using a docker desktop and I have been running the Pi Node for a month now.