No matter what I do, filebrowser insists my config does not exist and will not start with anything but the default configuration. #805
Replies: 3 comments 2 replies
-
|
If I use the mount:
And remove the env variable specifying the conf, it starts, but with the error: '[error] could not open config file 'config.yaml', using default settings' |
Beta Was this translation helpful? Give feedback.
-
|
according to the docs, if you run the container with a different user, you also need to mount a tmp directory |
Beta Was this translation helpful? Give feedback.
-
|
After about three hours on and off messing with this, I finally found my problem.
Must NOT be encapsulated in quotation marks. Removed those and it works as you'd expect. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Here is the contents of /srv/filebrowser-new/data/config.yaml this file and the folder that contains it both have 777 permissions.
server:
port: 80
baseURL: "/"
logging:
- levels: "info|warning|error"
sources:
- path: "/folder"
userDefaults:
preview:
image: true
popup: true
video: false
office: false
highQuality: false
darkMode: true
disableSettings: false
singleClick: false
permissions:
admin: false
modify: false
share: false
api: false
auth:
adminUsername: -redacted-
adminPassword: -redacted-
Then there's my docker compose file:
services:
filebrowser-new:
image: gtstef/filebrowser:latest
user: 1000:1000
container_name: filebrowser-new
environment:
- TZ=America/Vancouver
- FILEBROWSER_CONFIG="/config/config.yaml"
volumes:
- /srv/filebrowser-new/data:/config
- /home/darkassassin07:/folder
restart: always
networks:
arr:
ipv4_address: 172.18.0.122
networks:
arr:
external: true
Trying to start this gives the error "/config/config.yaml does not exist." I've tried putting it in different folders both inside and outside the container, tried mounting the full file path (/srv/filebrowser-new/data/config.yaml), tried mounting it overtop of the default /home/filebrowser/data/config.yaml in the container with and without specifying with the env variable, nothing works.
If I swap out the image for hurlenkos filebrowser, it starts; then I can use docker exec to ls the files and /config/config.yaml 100% exists and has 777 perms inside the container with the above config files. I can see the file myself and verify it has completely open permissions, but filebrowser insists it doesn't exist at all and will not start.
The only way I can get the container with this image to start at all is by removing the env variable specifying the config, where it then loads a default config that I cannot change.
Beta Was this translation helpful? Give feedback.
All reactions