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.

Sign up for GitHub

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

Jump to bottom

Update command should automatically prune old nextstrain/base images #23

Closed
tsibley opened this issue Aug 6, 2018 · 0 comments
Closed

Update command should automatically prune old nextstrain/base images #23

tsibley opened this issue Aug 6, 2018 · 0 comments
Assignees
@tsibley

Comments

@tsibley
Copy link
Member

tsibley commented Aug 6, 2018

Otherwise we're setting our users up for massive essentially-hidden disk usage.
@tsibley tsibley self-assigned this Aug 6, 2018
tsibley added a commit that referenced this issue Aug 8, 2018
@tsibley
runner.docker: Prune our old images after pull in update()
fa6bf4e 
Otherwise the previous images are left around, using up potentially
quite a lot of disk space in a not-very-visible way.

Note that this requires labeled versions of nextstrain/base, so images
before that point won't ever be automatically pruned.  They have to be
manually cleaned up as a one-time step.

One downside of this is that locally built images which are only tagged
with "latest" will be removed when `nextstrain update` is run.
Protecting them requires tagging them with an additional value by
running `./devel/tag local-dev` in the docker-base repo, for example.

Resolves #23.
@tsibley tsibley mentioned this issue Aug 8, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tsibley tsibley

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tsibley