On boot exit 2 after that no problem
See original GitHub issueHi,
i hope that somebody can help me. When i reboot/start my server, all Containers start, except nginx-proxy. There i get an “Exited (2)” in the status. After i make an “docker-compose up -d” it starts und runs without any problems. The logs don´t tell my anything (at least for me as a docker beginner).
`SIGQUIT: quit PC=0x46b9e1 m=0 sigcode=0
goroutine 34 [syscall]:`
And than a lot of goroutine´s.
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (11 by maintainers)
Top Results From Across the Web
How to perform a clean boot in Windows - Microsoft Support
On the General tab, select Normal Startup. Select the Services tab, clear the check box beside Hide all Microsoft services, select Enable all,...
Read more >Stuck at GRUB command line - boot - Ask Ubuntu
You got a problem with the bootloader. You should initialize kernel. First use command ls , then adjust the following commands according to...
Read more >Can't exit diagnostics - Can't boot windows - Dell Community
I was having a problem with windows locking up so I pressed F12 after the Dell logo and ran the diagnostics. No problem...
Read more >GRUB starts in command line after reboot
If entering 'exit' on the GRUB command prompt brings you to the GRUB menu, it could be an issue with the boot priority...
Read more >Troubleshooting - My Computer Won't Boot Windows - Intel
If you're still having trouble getting into your OS after exploring and addressing any error messages, it might be time to reset your...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Don’t be, everything’s fine 😄
Well to be honest my take on that is that the compose file is provided as a bare bone example only. Adding a
restart:
directive would be making assumptions on the user’s behalf. That’s everyone responsibility to familiarise themselves with the specific of the other tools involved in a project (Docker CLI or Docker Compose in this case).Hi. This might be an issue with docker-gen that should have been fixed recently, but the updated docker-gen version is not used yet in nginx-proxy. I’ll try to push a (supposedly) fixed container for you to try in the next days.