Back to Tutorials
Container File Browser
Navigate the container filesystem, upload files to a container, and download files from a container.
Prerequisites
- Docker is running
- A running container exists
Scenario 1: Browse Container Files
- Click Containers in the sidebar
- Find the running container in the list
- Click the folder icon ("Browse Files") on the container row
- The file browser opens at the container's root (
/) - Click folders to navigate deeper (e.g.,
/etc,/var/log,/app) - Files show their name, size, permissions, and last modified date
- Click the back arrow or breadcrumb path to navigate up
Scenario 2: Upload a File to a Container
- Open the container's file browser (folder icon on the container row)
- Navigate to the target directory (e.g.,
/usr/share/nginx/html) — make sure the directory is not on a read-only mount - Click the Upload button (arrow-up icon)
- A file picker dialog opens — select a file from your Mac
- The file is copied into the container at the current directory
- The file browser refreshes to show the uploaded file
Scenario 3: Download a File from a Container
- Open the container's file browser
- Navigate to the file you want to download
- Right-click the file (or click the ... menu on the file row)
- Click Download
- A save dialog opens — choose where to save the file on your Mac
- The file is copied from the container to your local filesystem
What You'll See
- The file browser displays a familiar Finder-like interface with columns for name, size, and modification date
- Directories show a folder icon, files show type-appropriate icons
- The current path is displayed as a breadcrumb bar at the top
- Upload and download operations show a progress indicator for large files
Tips
- File operations use
docker cpunder the hood — this works with both running and stopped containers - You cannot edit files in-place within the file browser — download, edit locally, then upload back
- For bulk file operations, consider using a bind mount instead (see the Run a Container tutorial)
- System directories like
/procand/sysare virtual filesystems and cannot be meaningfully browsed