Tinyfilemanager Docker Compose [patched] Jun 2026

To deploy using Docker Compose, you can use the official image tinyfilemanager/tinyfilemanager . This setup allows you to manage files on your host machine through a lightweight web interface. Docker Compose Configuration

You can set parameters like the timezone ( TZ ) or user IDs ( PUID / PGID ) via environment variables if using specific community images like moonbuggy2000/tinyfilemanager .

location / proxy_pass http://tinyfilemanager:80; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; tinyfilemanager docker compose

TinyFileManager is a lightweight, web-based file manager written in PHP. It features a sleek interface, built-in file editing, an archive manager, and multi-user support. Running TinyFileManager inside a Docker container using Docker Compose simplifies deployment, ensures cross-platform consistency, and isolates your application dependencies.

:Run the following command in the same directory: docker compose up -d Use code with caution. Copied to clipboard Important Details Access : Open your browser and go to http://localhost:8080 . Default Credentials : Admin : admin / admin@123 User : user / 12345 To deploy using Docker Compose, you can use

version: '3.8'

Set ownership of the mapped storage folder to match standard web server permissions: sudo chown -R 33:33 ./data sudo chmod -R 775 ./data Use code with caution. :Run the following command in the same directory:

When using Docker volumes, ensure that file permissions are correctly set. The Nginx-based version allows you to specify the user ID (PUID) and group ID (PGID) to run the container:

Within your project directory, create a file named docker-compose.yml and open it in a text editor. Add the following configuration:

Always change the default login credentials after your first login. The default credentials (admin/admin@123 and user/12345) are well-known and pose a significant security risk if left unchanged.

FM_ROOT_PATH explicitly tells the application to restrict user navigation to your mapped data volume, preventing directory traversal leaks into the internal container structure. Hardening and Security Configurations