Skip to content
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

Add --force flag to --update-container to force the update even if there's no new version #14

Closed
StayPirate opened this issue Nov 22, 2021 · 0 comments

Comments

@StayPirate
Copy link
Owner

Having the possibility to force an update when a new version is not available will help to get the latest container-image built which might contains updated packages version installed.

StayPirate added a commit that referenced this issue Nov 22, 2021
It might happen that you want to replace the current container with a
new one based on the latest container-image built. For instance, this
can be handy when a new version of a package (installed in the image) is
released but the image itself hasn't got any version bump.
You can now use `secbox --update-container --force` to pull the latest
image built and replace the container with one based on that image.

Fixes #14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant