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

Upgrade the currently installed container image #1066

Open
almet opened this issue Jan 30, 2025 · 0 comments
Open

Upgrade the currently installed container image #1066

almet opened this issue Jan 30, 2025 · 0 comments
Labels
icu Issues related with independent container updates
Milestone

Comments

@almet
Copy link
Member

almet commented Jan 30, 2025

When a new image is released on the container registry, we should be able to detect it, verify its signature against a locally known public key and install it.

We currently have a mechanism in place to detect new dangerzone versions (not container images), and this should probably be an extension of it.

When installing a new image, we should also delete the old one, to save space

Open questions:

  • Should we have a specific setting to allow container image updates in-place, or should we rely on the fact that the user has allowed checking for updates?
@almet almet added the icu Issues related with independent container updates label Jan 30, 2025
@almet almet added this to the 0.9.0 milestone Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
icu Issues related with independent container updates
Projects
Status: Todo
Development

No branches or pull requests

1 participant