I don’t know what happened, but I’m not able any longer to execute bitwarden.sh.
The error message is:
IOError: [Errno 2] No such file or directory: u’/var/services/homes//bwdata/docker/docker-compose.yml’
I never had any config files unter homes (they are located directly in several docker/bwdata directories.
Any idea, where this changes behaviour is coming from and how to fix?
Thanks,
Kingshill
PS: If I create all requested entries under /homes on my synology manually, I the the error
“couldn’t connect to Docker deamon at http+docker://localunixsocket - is it running? If it’s a non-standard location, specify the URL with the Docker_HOST env variable”
If you open the Control Panel in the Synology webgui, do you have a shared folder called “homes”? Does the volume listed match the target on the /var/services/homes symlink?
I don’t have BW on my NAS (it’s too old) so I can’t help you with that bit.
Thanks for your answer. I have updated my question already, to be more precise:
Yes, I have the home directories activated on Synology. However, they BW installation has never created any of those env files (e.g. mssql, global and the related override files) within the homes, but in the bw installation directory (which is /docker/bwdata/…).
So I’m confused, why the bitwarden.sh is now pointing to the homes directory.
Ah! I thought your BW had stopped working as well
So only the bitwarden.sh script. Maybe it’s not the right one?
On my machine, bwdata folder was created in the same folder where I ran ./bitwarden.sh install When reading the script it looks like they try quite hard to ensure that.
Is there a /docker/bitwarden.sh maybe?
Or maybe try and copy it there?
Looking at my /root/bitwarden.sh, how it calls /root/bwdata/scripts/run.sh and how run.sh exports COMPOSE_FILE="$DOCKER_DIR/docker-compose.yml", I simply cannot understand how this is possible.
What does your /docker look like? Is it a folder or symlink? (ls -ld /docker)