Standalone docker guide (v1.5.x and earlier)
This guide will help you set up your FileBrowser v1.5.x and earlier instance alone. This will be helpful for users who just want to access their files over LAN for storage.
This guide is for v1.5.x and older (stable). It uses the stable Docker image and the legacy database (database.db) for the database.
Looking for v2.0.0 (beta)? See the v2.0.0 standalone guide instead.
Planning to upgrade to v2.0.0?
v2.0.0 replaces the legacy database with a new database format and requires a one-time migration. Do not switch your image tag until you have read and followed the v2 migration guide.
Folder Structure
Initial Setup
- Run the commands below commands in the terminal to initialize the folder structure, or manually via the desktop.
Volume bindings needed:
./data:/home/filebrowser/datais required to set the config file, database and tmp folder.- Any folder you want to have access to. In this example, we use
./fileswhich will be created in the same directory - Other volume bindings that need to have access via the web.
Update the compose.yml,
| |
To pin a specific v1 release instead of tracking the latest stable, use a version tag such as 1.5-stable or 1.5.5-stable. See Docker version tags.
Update the config.yaml,
| |
Running container with a different user
On v1.2.x and earlier, the default user is root.
On v1.3.x and later, the default user is filebrowser (1000:1000).
The easist way to update the user is through docker compose. For example to create a new user 1001:1001 “${UID}:${GID}”:
You will also want to ensure the data folder has the correct permissions with chown command:
| |
Using FileBrowser
Starting the service
Change to the directory where the compose file is in your terminal and run,
| |
This will pull the image and start the container. You can now access it via http://<YOUR_IP>:8900.
Updating the service
Change to the directory where the compose file is in your terminal and run,
With the database and cache set up, your data will persist even with restarts.