-
Notifications
You must be signed in to change notification settings - Fork 10
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
Could not restore network resources for running containers #163
Comments
The problem was caused by the stored network setting, they were persisted in some intermediate state. The problem was fixed by deleting the network storage. Could not reproduce the issue and find the initial reason for it's occurrence. |
I think this issue should stay open for further checks because I got the same problem.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Network could not be restored upon container-management start. Once the error pop up it persists even after container-management restart. As a result containers with bridge network could not be started.
The text was updated successfully, but these errors were encountered: