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
Failed to apply configuration for the following parameters: network_mode #41765
Comments
I am unable to replicate this error using different container images to simulate an update. Could you provide me with some steps to replicate this issue? Thanks, |
My dockerfile is:
I think this part is sufficient to replicate the issue:
|
Hrm, I am stlll unable to replicate this issue.
And I am on 2016.11.5, it looks like network_mode might be set to bridge by default. |
I think this is the problem because you can't replicate. Try to build and run with the same tag. |
If I used the same version, then it just starts it again.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Description of Issue/Question
dockerng.running restarts my images every time (as expected) but fails giving this error:
Failed to apply configuration for the following parameters: network_mode
Setup
Steps to Reproduce Issue
The first run just works fine, but the second run i get the following error:
I added "- network_mode: bridge", but adding it fixed the error label but not start the container.
If i look in the debug log of salt i see the following:
2017-06-15 13:49:28,130 [salt.state ][ERROR ][14120] {'diff': {}, 'state': {'new': 'running', 'old': 'stopped'}, 'removed': [u'c9eb5b927976c5d594f46d64a83ee2c38f49672555a37bd846f7f8ee468b710e'], 'added': {'Time_Elapsed': 0.29279398918151855, 'Name': 'application', u'Id': u'5a69709cc7e49a961032a58268d25d67d663ffe263f7341a4637a43ee487ae57', u'Warnings': None}}
Versions Report
The text was updated successfully, but these errors were encountered: