Add dist-upgrade to the Dockerfile about docker-redmine HOT 7 CLOSED

I think you must update and upgrade image, but not the container.
Just do "docker pull debian:jessie && docker build -t yourname/redmine ." regularly

from docker-redmine.

Well, docker-redmine is inherited FROM sameersbn/ubuntu:14.04.20141001, so I believe without modifying Dockerfile it won't work. I think Sameer updates this base image periodically, so 'dist-upgrade' is just a handy option for those who rebuild image between those snapshots, but wants to have system up-to-date...

from docker-redmine.

https://github.com/sameersbn/docker-redmine/releases/tag/v2.5.2-3
upgrade to sameersbn/debian:jessie.20141001

from docker-redmine.

@b-a-t @elderone Performing apt-get upgrade or apt-get dist-upgrade in a container is not advised by docker developers. For the simple reason that it can break the image altogether. Refer docker best practices post by crosbymichael who is a core developer of the docker project.

To be honest, I used to perform apt-get upgrade in the dockerfiles of my projects. Since the above post I have stopped doing it.

from docker-redmine.

@sameersbn I see your reasoning. Well, I guess have to stick to it :)

Speaking of common practices, https://docs.docker.com/faq/#why-is-debian_frontendnoninteractive-discouraged-in-dockerfiles discourage from using:

ENV DEBIAN_FRONTEND noninteractive

from docker-redmine.

BTW, latest now uses ubuntu14.04 as a base image, and 2.5.2-3 uses debian:jessie. So which one is going to be mainstream for docker-redmine now?

from docker-redmine.

@b-a-t thanks for the info on the use of ENV DEBIAN_FRONTEND noninteractive. I will remove it from the base image.

So which one is going to be mainstream for docker-redmine now?

The switch to ubuntu:14:04 is the one I will be sticking by. No more base image changes. Please refer to my comment if you are interesting in knowing why I made the switch

from docker-redmine.