-
Notifications
You must be signed in to change notification settings - Fork 385
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
create: config to pull latest image by default #289
Conversation
Hi @juhp thanks! |
Using it a bit, we might want to change a bit the behavior on this Right now, every time I So either we could (as you proposed in #289 ) to have a That would also set the non_interactive to 1, so that it does not ask questions What do you think? |
Thanks for testing - I only really tried the default interactive case myself so far.
Correct
Do you mean it doesn't make sense if one already has the latest?
So now "No" meant don't pull a new image (it is pretty similar to the old behavior with an existing image).
Okay, thanks, sounds good enough to me, let's try that then. |
Thanks to you for the PR 😄
Yep should be less confusing, maintaining the current behavior (in |
How about this then? |
Great exactly what I was thinking 😄 There is one error for undefined variable in the code Man pages are automatically generated from that change, so no need to recreate them yourself 👍 |
…uca89#288) If either DBX_CONTAINER_ALWAYS_PULL or container_always_pull in config is set, 'create' will pull the latest image without prompting (even if image already exists locally). Use this to ensure the new toolbox is based on the most current image instead of an old out-dated one.
Ah yes thanks - hopefully better now and added more docs coverage. |
Thanks a lot for the contribution! |
Thanks for your help too :-) |
This is a potential solution to #288, which gives
the user the chance to always create a new toolbox with
the latest most current image, instead of an old out-dated one.