You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having trouble reading from a folder under /var/ (on the host) from docker and am suspecting that it might be a colima thing. If not, please let me know.
I am running a local backstage instance and noticed that it can't read the temp files backstage generates to /var/folders/wt/*/T/backstage-*. Unfortunately I don't see where I could change the path where these temp files are stored. So I tried cding into the directory in question and running a little test:
but if I run an ls -l in a docker container, I only see site
➜ backstage-N4zMz6 docker run --rm -w /content -v "/private/var/folders/wt/3z9vk6f57v9d6dqzlkp_xxm00000gn/T/backstage-N4zMz6:/content" ubuntu ls -l
total 4
drwxr-xr-x 2 root root 4096 Apr 29 06:10 site
Why can't I see the other files in the docker container? Can someone point me in the right direction here?
From reading around a bit I made sure that the folder is the filesharingDirectories array in ~/Library/Group\ Containers/group.com.docker/settings.json, but that didn't change anything.
Description
I'm having trouble reading from a folder under /var/ (on the host) from docker and am suspecting that it might be a colima thing. If not, please let me know.
I am running a local backstage instance and noticed that it can't read the temp files backstage generates to
/var/folders/wt/*/T/backstage-*
. Unfortunately I don't see where I could change the path where these temp files are stored. So I triedcd
ing into the directory in question and running a little test:(output as expected)
but if I run an
ls -l
in a docker container, I only seesite
Why can't I see the other files in the docker container? Can someone point me in the right direction here?
From reading around a bit I made sure that the folder is the
filesharingDirectories
array in~/Library/Group\ Containers/group.com.docker/settings.json
, but that didn't change anything.Thanks ❤️
Version
colima version HEAD-9b0809d
git commit: 9b0809d
runtime: docker
arch: aarch64
client: v25.0.4
server: v24.0.9
limactl version 0.21.0
qemu-img version 8.2.1
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers
Operating System
Output of
colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/chle/.colima/default/docker.sock
Reproduction Steps
As described, don't know if others can reproduce this
Expected behaviour
I see all the files and folders in the
ls -l
ran in the docker containerAdditional context
No response
The text was updated successfully, but these errors were encountered: