Files
Open a service's Files tile to browse the files inside its running container: open folders, read text files, download files, upload a file, create a folder, rename and delete.
The file browser works on the service's newest running instance, through the same channel as the Command and Terminal tiles. It is available once the service is deployed and running.
What you can do
| Action | How |
|---|---|
| Browse | Click a folder, use the path above the list, or type a path and press Go. The list shows each entry's size, permissions (like ls -l) and modification time; hover the permissions to see the owner. |
| Read | Click a file to show it. Text files are shown up to their first 256 KB; binary files can only be downloaded. |
| Download | The download button next to a file, or Download in the viewer. Files up to 500 MB. |
| Upload | Upload, or drop a file onto the list. It goes into the folder you are looking at. Files up to 50 MB, one at a time. If a file with the same name exists, you are asked before it is replaced. |
| New folder, rename | New folder, and the pencil button next to an entry. Renaming keeps the entry in the same folder. |
| Delete | The trash button, then Delete to confirm. A folder is deleted with everything in it; a link is removed without touching what it points to. Deleting cannot be undone. |
Volumes and lost changes
A container's files outside a volume come from its image and start fresh on every redeploy or restart. The file browser says so above the list and names the service's volumes; inside a volume it says the changes are kept. Volume folders are marked Volume in the list.
Use the file browser to inspect a service, pull a file out, or put data into a volume. To change files that should stay changed outside a volume, change the image or add a config file on the service's Settings tab instead. Config files are mounted read-only, so they cannot be changed here.
Requirements
The container needs a shell (sh) and the usual file tools (cat, stat, mv, rm, mkdir, wc), which every image based on Alpine, BusyBox, Debian or Ubuntu has. Minimal images such as distroless or scratch contain only the application; for those the file browser says the image has no shell. File operations run as the container's user, so a container that does not run as root may not be allowed to read or change some files.
Who can use it
Members, admins and owners. Viewers cannot open the file browser at all, not even to list files, because files can hold secrets such as keys and .env files.
Uploads, downloads, new folders, renames and deletes are recorded in the team's audit log with the service and the path. File contents are never recorded.
How it works
Each action runs one fixed script in the container with kubectl exec-style access from the control plane. Paths are cleaned (so .. cannot climb above /) and passed to the script as separate arguments, never inserted into a shell command, so names with spaces, quotes or $(…) are handled as plain names. Uploads stream into a temporary file next to the target and are moved into place only after every byte arrived; an interrupted upload leaves nothing behind. Downloads are sent as attachments that browsers never open as a web page.