I like the fact that Discourse runs inside a Docker container. However, I’m currently not willing to run this on a production system since it’s not clear to me how security updates inside the Docker container will be handled.
On a typical Ubuntu server installation I’ll enable unattended-upgrades to automatically install security updates or at least to notify me about updates (like when I’ve installed nginx from a PPA).
So, how will this work with the Discourse docker image. Will you configure unattended-upgrades to check for security updates and let it notify the admin or even install those updates automatically?
How will you handle updates for 3rd party packages like nginx? Those should be included in those checks (by default they aren’t).
And of course there’s software installed from source as well. How would those get updated if there’s a security vulnerability that needs fixing?
I’ve been looking how others are keeping their docker containers secure. However, it looks like that nobody cares or doesn’t use long running containers. The answer usually is “rebuild your container” .
Obviously that will only work
- if the Discourse admin gets notified that he needs to update the container
- and when there actually exists an updated docker image.
Are there any plans to automate security updates inside to container? That would be my preferred option. I couldn’t find anything about that in your spec for version 1.
Or are you planning to provide docker images that are always up-to-date and notify the users (email) when they need to upgrade the docker container?