![File browser (container)]()
File browser (container)
A web file manager
Image details
Source details
Configuration
TypeContainerlinuxfilebrowser/filebrowser:latest--port 80 --database /data/database.db --root /srv80/tcp/data/srvTemplate by portainer
Report issueNotes
Standalone Install
Select an install method, to see config/commands for deploying File browser (container)
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select File browser (container), fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see filebrowser/filebrowser for app-specific guidance.
Please check the main repository for more info.
Serve File browser (container) on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying file-browser-container.example.com to http://file-browser-container:80
Add this to your Caddyfile
file-browser-container.example.com {
reverse_proxy http://file-browser-container:80
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Published on a random port
This template exposes 80/tcp without setting a host port,
so Docker picks a random free one on every deploy.
- Find it in the Ports column of Portainer's container list, or with
docker port <container>
Image won't pull
Test the pull directly on the host: docker pull filebrowser/filebrowser:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64, arm/v7, arm/v6 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Upstream project is archived
The developers have archived filebrowser/filebrowser, so bugs and security issues won't be fixed.
- It'll keep working for now, but consider the similar apps below for a maintained alternative.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on filebrowser/filebrowser
- Template not working: Open an issue on portainer/templates
- This website not working: Open an issue on lissy93/portainer-templates
A single container
File browser (container) runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything File browser (container) needs bundled into one download. This template pulls filebrowser/filebrowser:latest, which Docker fetches once (about 45 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. File browser (container)'s comes from Docker Hub, published by filebrowser.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is v2.63.23-s6. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, arm/v6, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:
80, published on a random host port
Volumes
A volume is where File browser (container) keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/dataas a volume Docker manages for you/srvas a volume Docker manages for you
Networking
Nothing custom is set, so File browser (container) sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Startup command
The command is what runs the moment the container starts. This template sets its own, --port 80 --database /data/database.db --root /srv, in place of the image's default.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Open source license
File browser (container) is open source, released under the Apache-2.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set File browser (container) up. Add the template list to Portainer once, then deploying File browser (container) is a click rather than a wall of config.