linuxserver-archive / docker-baseimage Goto Github PK

It would be nice to have an environment variable for disabling the various chown calls throughout the various init scripts. This would apply to the docker-baseimage as well as all of its child images. This would be immensely useful (just like the PUID and PGID variables) for enabling easily transportable docker containers to the masses.

My experience:
While attempting to install linuxserver/docker-muximux, I was presented with the error

chown: changing ownership of '/config': Permission denied

This is because all of my docker volumes are mounted from a CIFS directory on the host machine. I have my NFS mounted with the uid/gid of nobody:nogroup, the same permissions I set for my docker containers.

The chown fails under this configuration, preventing me from using your images without manual intervention on my part. A simple environment variable toggle would readily fix this. The toggle might looks something like the following

if [ "$CHOWN_DISABLE" == "false" ]; then chown -R abc:abc /config; fi;

It appears that not all mirror sites are equal, seeing this a few times now, with sabnzbd, but i don't think it's something that would be particular to that one container, hence raising the issue here.

http://lime-technology.com/forum/index.php?topic=42441.msg426452#msg426452

E: Method gave invalid 103 Redirect message

one of the mirror repos is throwing that error and preventing update of SAB, consequently people are stuck on the version that is in the image.

an example is Mylar. when using the docker like normal, it pulls the main branch. what i propose is add a variable like gitbranch or branch, so when not used it defaults to main branch, and when used it calls the branch given. since this would be used by someone who wants/needs a specific branch i.e. develop/development there is no need to supply that to the user. this will help people using dockers for the holy trinity (sonarr, couchpotato, headphones/mylar) to troubleshoot or get issues resolved easier.

I think this is related to having to use

-o Dpkg::Options::="--force-confold" in the update section of the dockerfile for baseimage.

it's done so any packages that are updated that you would normally have to answer the dialog about keeping existing config file etc... is answered automatically by keeping the old one.

i think we may have to look at doing it by default in the update script, if i'm right about this of course...

mariadb is showing this now when trying to upgrade.

dpkg: error processing package mariadb-server-10.0 (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mariadb-server:
mariadb-server depends on mariadb-server-10.0 (= 10.0.23+maria-1~trusty); however:
Package mariadb-server-10.0 is not configured yet.

dpkg: error processing package mariadb-server (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mariadb-server-10.0
mariadb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)