-
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
Expose old config field for api < 1.19 #13675
Conversation
Signed-off-by: Antonio Murdaca <me@runcom.ninja>
LGTM |
One comment, it's not really an issue for me, but I know some people will complain. When talking to the daemon using the API 1.18, you the the resources both in Using This is the inspect:
As you can see |
@vieux I'm aware of this (while testing I came with your extact situation) but I think new fields are always exposed to older api so I didn't care. Is this really a problem? (I can find a way to fix this by masking HostConfig to a |
@runcom it's fine by me, I juste wanted to make sure you were aware. LGTM |
@vieux that happens with docker 1.6.1 too because those fields where duplicated:
|
@calavera ok thanks! |
Expose old config field for api < 1.19
🍰 |
cherry-picked |
/cc @icecrime @calavera @aanand
I tried everything (99.9999% sure) before going with a second function just for < 1.19 code path 👼
fixes #13663
Signed-off-by: Antonio Murdaca me@runcom.ninja