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

How do we manage security updates? #1

Closed
akafred opened this issue Jan 6, 2015 · 2 comments
Closed

How do we manage security updates? #1

akafred opened this issue Jan 6, 2015 · 2 comments

Comments

@akafred
Copy link
Contributor

akafred commented Jan 6, 2015

(Question from theodotos – found here: https://registry.hub.docker.com/u/digibib/koha/ )
@akafred
Copy link
Contributor Author

akafred commented Jan 6, 2015

We're building this container on every commit (using make all command in the root of the git repo), but to speed up builds we use Docker's caching mechanism so not all layers are built from scratch. This means there will be some outdated debian packages after a while (this is debian stable so things are pretty ... stable). We consider this not too critical as we expose few services from the container. For Koha we are generally updating to the latest stable Koha release within days.

We should consider using an ENV UPDATED_AT yyyy-mm-dd entry high up in the Docker file – or build each image from scratch ...

@akafred
Copy link
Contributor Author

akafred commented Jan 7, 2015

Seems we already have addressed this to some extent by including ENV UPDATED_AT in Docker file. I have refreshed in ab19ba6 .

@akafred akafred closed this as completed Jan 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@akafred