-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
Fix container register failed during daemon start and then start the container #16275
Conversation
@@ -315,6 +315,8 @@ func (daemon *Daemon) restore() error { | |||
|
|||
if err := daemon.Register(container); err != nil { | |||
logrus.Debugf("Failed to register container %s: %s", container.ID, err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the log level should be "ERROR" instead of "DEBUG".
Otherwise we have to ask the user to switch on the debug flag to report such kind of bugs, which is a bit inconvenient.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mountkin Agree . thanks :-)
21beca9
to
b4841dd
Compare
…e container Signed-off-by: Lei Jitang <leijitang@huawei.com>
@coolljt0725 , Thanks for whipping up this patch. I look forward to using this to fix my problem (#14199). Can you point me to the guide on how to build this branch locally so I can test this on my system? How risky is it to run MASTER ? I suppose I could apply this patch to the |
@ChrisRut I think we should wait the Maintainers to review and confirm this is the right fix. :-) |
Fair enough 🔜... |
LGTM |
LGTM |
Fix container register failed during daemon start and then start the container
Signed-off-by: Lei Jitang leijitang@huawei.com
The container register failed during daemon starting should not be
started even if it has a restart policy
Fixes #14199