Thanks for the follow up @ralfaro
Yep created it as I always do, from my host user. I use the exact same process as defined by you guys above on all of my other containers. However Home Assistant just refuses to deploy properly haha.
Just for sanity and to write out my setup/approach in black and white to see if its something stupid that I am doing.
I have setup my UID’s and GID’s as per my synology NAS because it wont let me define the UID and GID and its assigned by itself. So for ease of file shares/NFS etc. I created a
dockeruser and assigned that user to group
dockeruser UID = 1039
group user GID = 100
I have then replicated all of this on my ubuntu server
dockeruser permissions to
docker so that user can deploy containers etc.
All of my docker mount directories reside in
/data/Docker and that is the
adduser --uid 1039 -gid 100 --home /data/Docker dockeruser
ls -l /data
drwxr-xr-x 13 dockeruser users 4096 May 21 13:48 Docker
/data/Docker/home-assistant directory is then created by dockeruser. Obviously my above examples are just me trying different things and simplifying everything back down, which still fails.
Below is a list of two users and what groups they belong to, my main user and dockeruser, I have even added dockeruser to sudo group just to see if that would do it! Clutching at straws there lol.
[email protected]:~$ id
uid=1000(nickcj) gid=1000(nickcj) groups=1000(nickcj),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),108(lxd),999(docker)
[email protected]:~$ id dockeruser
uid=1039(dockeruser) gid=100(users) groups=100(users),27(sudo),999(docker)
I have tried also to deploy this from my main user
nickcj who’s home directory is standard
/home/nickcj and using
I have also tried bind mounting
/etc/passwd:/etc/passwd:ro to see if the issue is due to the fact that those users don’t exist in the container so causing issues that way…nothing!
Any ideas, really would be welcomed