I'm breaking this off from another post because I'm not sure and I think its worth some explanation.

 

A lot of the dockers we use install through apt-get.  The latest example is SABnzbdplus and FFMPEG in the NZBGet dockers.  The DockerMan "Update" button doesn't see this update, I'm guessing because it looks at Docker build info.  What is the best way to notify and keep dockers up to date that install through apt-get.

Have an automated build process such that the Docker rebuilds when it detects major dependency updates. This should trigger DockerMan that there is an update. I think GFJardim has something similar to this for the Dockers he's put together.

 

The other means is to have the Docker authors go out of their way, such as Needo/GFJardim have, and included self-updating mechanisms inside the docker.

 

However, this goes against the nature of Docker containers. Each specific label of a Docker should be identical. The unRAID community is really abusing the concept of Dockers and tags/versions. If I create a Docker in November and then do so again in December, they should be exactly identical. This isn't the case with unRAID because the only labels the community tends to use is 'latest' and it's always bleeding edge.

 

What would be nice to have is the application developers themselves produce and maintain their own Dockers. When they push out updates, they update their application's Docker directly.

 

Ideal long term goal of what is really needed is for unRAID to be installed on a platform that has a real active community package management system, such as apt-get, so the users can update the applications directly themselves.

 

 

 

Have an automated build process such that the Docker rebuilds when it detects major dependency updates. This should trigger DockerMan that there is an update. I think GFJardim has something similar to this for the Dockers he's put together.

 

The other means is to have the Docker authors go out of their way, such as Needo/GFJardim, have and included self-updating mechanisms inside the docker.

 

However, this goes against the nature of Docker containers. Each specific label of a Docker should be identical. The unRAID community is really abusing the concept of Dockers and tags/versions. If I create a Docker in November and then do so again in December, they should be exactly identical. This isn't the case with unRAID because the only labels the community tends to use is 'latest' and it's always bleeding edge.

 

What would be nice to have is the application developers themselves produce and maintain their own Dockers. When they push out updates, they update their application's Docker directly.

 

Ideal long term goal of what is really needed is for unRAID to be installed on a platform that has a real active community package management system, such as apt-get, so the users can update the applications directly themselves.

 

Yes, I have automated build process on mine, but that only checks if the GIT is updated (or I don't know a way to have it check apt-get)  Does it check to see if the apt-gets are updated?