-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container not start after Host reboot (Exit code 127) #4
Comments
Is there nothing more in the log than what is visible in the screenshot? Because I would expect some message about why it is quitting? |
I have see in /var/log but the folder IS empty... Journal is it in another
folder ?
Le mar. 21 mai 2024, 17:10, Kroese ***@***.***> a écrit :
… Is there nothing more in the log than what is visible in the screenshot?
Because I would expect some message about why it is quitting?
—
Reply to this email directly, view it on GitHub
<#4 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA3TIMEAKC26TEDYAVH7ADZDNPU3AVCNFSM6AAAAABIBXPPTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRSHA2TMMBVGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I ment the Docker log! |
I have a suspicion this Docker log is from the last time the container run (so BEFORE the reboot) and not from when it was started (AFTER the reboot). The reason for this is that you have But in your case that is not happening, so there seems to be a problem with Docker before it even tries to start the container. For example: if the ip/ports are already in use, or it cannot read the mount directory, it will fail to start the container, but it does not keep retrying in that case, because it was not the container that failed, but Docker itself). Your issue seems very similar to an issue like: rancher-sandbox/rancher-desktop#4286 in which case it was also not related to the container itself. I have no experience with Docker desktop, or where to view the general log of Docker (instead of the container log). But the quickest way to debug this issue would be to remove almost everything from the compose file (the IP adress, the ports, the volumes) and reboot the machine and see if it starts. And when it starts, slowly keep adding those lines again until it stops again on reboot. That way you at least get an idea which part of the compose file is related to the issue. |
Ok... i have take docker daemon log here :
I don't understand why it can't mount file... :S |
I think because you use relative paths in your compose file. This means that the location will be dependant on what folder is your working directory while running So the solution is to use the full path in your compose, for example |
Thanks you for your help... According from daemon log file i have found theses issues : It seems it's a docker desktop bug on windows... :S A workaround will be to start docker from scheduler task instead of docker embed settings. |
My config:
Here my docker compose file :
All works perfectly... after host reboot... the container have exit code 127 :
If i start manually the container its works.
Have you an idea how to fix it please ?
Thanks
The text was updated successfully, but these errors were encountered: