I'm having some trouble / strange behaviour mapping OMV5 SMB/CIFS shares to docker volumes to run an instance of HomeAssistant.
Local docker volume seems to work perfectly but the OMV shared volume fails.
I'm hoping this is a common problem people have experienced and overcome with OMV, HomeAssistant and docker volumes.
Any thoughts, Ideas or wisdom would be appreciated .
Problem Details:
SETUP:
I'm attempting to create and instance of HomeAssistant in docker via Portainer
I would like the /config directory/files to live on OMV5 SMB/CIFS share /Data/HomeAssistant
I'm attempting to do this via a docker volume (not a bind, there appears to be some debate on the correct way to do this but docker seem to recommend volumes over binds but happy to hear alternative recommendations)
Portainer looks like it can create a Volume using CIFS (/Data/HomeAssistant)
Portainer can then map this Volume to /config and added it to a Docker Container and appears to start
Network = Host
restart policy = unless stopped
Docker installed on OMV5 - extras
PROBLEM:
/Config data does populate the OMV share CIFS (/Data/HomeAssistant) - this was confirmed via finder
BUT HomeAssistant Web Access doesn't appear to start eg ipAddress:8123 (standard HomeAssistant web port)
ATTEMPTED SOLUTIONS:
- Explicitly Map port 8123:8123 --> doesn't help
- Install HomeAssistant with the same config but with a local volume eg not a shared volume --> works perfectly as expected on ipAddress:8123