Skip to content

File download fails for paths on mounted volumes (“copy: path not found” in rootfs) #27

Closed

Description

Hi!

First of all, thank you for Davit! It’s a great app and makes working with Apple’s container platform a real pleasure.

Description
Downloading a file from the Files browser fails when the file is on a mounted volume. Davit seems to resolve the path against the container’s root filesystem (/run/container//rootfs/...) instead of the path as seen inside the running container, so files on volumes are not found.

Steps to reproduce

Run a container with a named volume mounted at /home/dev.
Create a file inside the container, e.g. echo test > /home/dev/testfile.txt.
In Davit, open the container’s Files tab, navigate to /home/dev and download testfile.txt.

Expected: The file is downloaded to the Mac.

Actual: The download fails with:

internalError: "failed to copy from container " (cause: "internalError: "failed to copy from container (cause: "unknown: "notFound: "copy: path not found '/run/container//rootfs/home/dev/testfile.txt'""")"")

Additional observations

The file exists and is readable inside the container (container exec ls -l /home/dev/testfile.txt works).
Copying the same file to /tmp (not on a mount) and downloading it from there works fine.
The Files browser lists the file on the volume correctly. Only the download fails.

Workaround
Copy the file to a path that isn’t mounted first.

Environment

Davit version: 0.1.38
container platform version: 1.3.1
macOS version: Golden Gate 27.0.1
Mac model / chip: MacBook Pro / Apple M3 Pro

Thanks again for your work on this!
Martin

Activity

  1. wouterdebie commented on Oct 27, 2026

    @wouterdebie
    Owner

    Thanks for the clear report, Martin. This is fixed in v0.1.39 (Davit -> Check for Updates, or brew upgrade --cask davit).

    The cause was upstream: the platform's copy looks for the path in the container's root filesystem, underneath any mounts (apple/container#1873), so a file on a volume is never found. Davit now streams files on mounted paths through the container itself instead.

    The same bug also hit uploads to a mounted path: they reported success, but the file never showed up in the container. That's fixed too, including uploads in the volume browser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions