Closed e-e-eric closed 1 week ago
Hi @e-e-eric
Can you share your docker-compose.yaml
please?
Also what Operating system are you using Budibase on?
Hi @shogunpurple,
I am running on TrueNAS Scale (appliance) so it is using Debian 12 with Kubernetes under the hood.
The only environment variable I have defined is INTERNAL_API_KEY. Storage is Host Path attached volume (bind mount).
It is equivalent to the following: ` services: budibase: restart: unless-stopped image: budibase/budibase:latest ports:
As reported above, it installs fine onto a volume mount, and runs fine from a bind mount. It just doesn't install to the volume mount. My guess would be probably due to an unnecessary permissions check somewhere.
Cheers
@e-e-eric so are you using kubernetes? How are you deploying the docker-compose setup on that?
I'll need more information about exactly:
As reported above, it installs fine onto a volume mount, and runs fine from a bind mount. It just doesn't install to the volume mount.
So does it install to the volume mount, or not? I'm sorry, but it would be helpful to be clear about exactly what is happening
@shogunpurple Apologies, title was incorrectly labelled as volume mount (now fixed). My report is that the image doesn't install correctly to bind mount, and that a volume mount is required. Once installed to a volume mount, moving the data to a bind mount runs as intended. This suggests a permissions check somewhere in the install script is hard failing unnecessarily.
I'm just using the TrueNAS GUI to run the equivalent parameters.
Install steps on TrueNAS
Image repository: budibase/budibase Image Tag: latest
Container Environment Variables:
variable: INTERNAL_API_KEY
value:
Storage > Host Path Volumes: Host Path: /bindmount/data Mount Path: /data
Please feel free to close if you can't replicate on your test host.
@e-e-eric I have not been able to repro this with a local docker setup. There's a chance that your TrueNAS configuration isn't setting the bindmount correctly or there's some environmental issue preventing it. Closing for now but I would try on a different env to see if you are still having the same issue.
Checklist
Hosting
Describe the bug Brand new docker image does not install (standard yaml, only API variable and volume mount).
To Reproduce Docker compose with volume mount for /data
Expected behavior Install correctly.
Screenshots drwxrwx--- 4 5984 5984 4 Jul 31 13:05 couch drwxrwx--- 3 root root 3 Jul 31 13:05 minio drwxrwx--- 2 root root 2 Jul 31 13:05 search
/couch drwxrwx--- 2 5984 5984 2 Jul 31 13:05 dbs drwxrwx--- 2 5984 5984 2 Jul 31 13:05 views
Additional context CouchDB appears to lack permissions. I checked permissions and ownership, all appeared well. Using a basic yaml with only the API variable and volume mount.
In my case, I resolved by letting CouchDB install to a volume, then moved the installed /data to the volume mount. Therefore, it appears CouchDB no longer installs correctly to a direct volume mount.