You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
container starts, listens on port 80 internally but Docker exposes that as port 8080 on the host
What I saw:
The empty filebrowser.db was initialized, changing into a 64kB file so I know the container can access $HOME/.filebrowser, but:
[custom-init] No custom files found, skipping...
[ls.io-init] done.
2023/08/12 21:18:47 No config file used
2023/08/12 21:18:47 Listening on 127.0.0.1:8080
Since the console output says it's listening on port 8080 instead of 80, I tried restarting the container with -p 8080:8080 but then I get "connection reset by peer"
The text was updated successfully, but these errors were encountered:
Following the instructions at https://filebrowser.org/installation#docker , the container image seems to ignore/skip the /config/settings.json file.
Steps to reproduce:
What I expected:
container starts, listens on port 80 internally but Docker exposes that as port 8080 on the host
What I saw:
The empty filebrowser.db was initialized, changing into a 64kB file so I know the container can access $HOME/.filebrowser, but:
Since the console output says it's listening on port 8080 instead of 80, I tried restarting the container with
-p 8080:8080
but then I get "connection reset by peer"The text was updated successfully, but these errors were encountered: