mkdir /path/lima/wks: read-only file system

[cmoulliard]

Description

Issue

I created successfully a docker VM using the command

limactl start https://raw.githubusercontent.com/afbjorklund/lima/master/examples/docker.yaml
...
INFO[0165] READY. Run `limactl shell docker` to open the shell. 
INFO[0165] To run `docker` on the host (assumes docker-cli is installed): 
INFO[0165] $ export DOCKER_HOST=unix:///Users/cmoullia/.lima/docker/sock/docker.sock 
INFO[0165] $ docker ...    

but when I launch a script able to install kind kubernetes then I got as response

docker: Error response from daemon: error while creating mount source path '/Users/cmoullia/code/snowdrop/infra-jobs-productization/k8s-infra/lima/wks': 
mkdir /Users/cmoullia/code/snowdrop/infra-jobs-productization/k8s-infra/lima/wks: read-only file system.

If I move under /tmp/lima, I got a permission denied docker: Error response from daemon: error while creating mount source path '/tmp/lima/wks': chown /tmp/lima/wks: permission denied.

Versions

Lima: limactl version 0.8.1
OS: Darwin MacBook-Pro 20.6.0

[afbjorklund]

The home directory is read-only, by default.

# Expose host directories to the guest, the mount point might be accessible from all UIDs in the guest
# Default: null
mounts:
- location: "~"
  # CAUTION: `writable` SHOULD be false for the home directory.
  # Setting `writable` to true is possible, but untested and dangerous.
  # Default: false
  writable: null
  sshfs:
    # Enabling the SSHFS cache will increase performance of the mounted filesystem, at
    # the cost of potentially not reflecting changes made on the host in a timely manner.
    # Default: false
    cache: null
    # SSHFS has an optional flag called 'follow_symlinks'. This allows mounts
    # to be properly resolved in the guest os and allow for access to the
    # contents of the symlink. As a result, symlinked files & folders on the Host
    # system will look and feel like regular files directories in the Guest OS.
    # Default: false
    followSymlinks: null
- location: "/tmp/lima"
  writable: true
  sshfs:
    followSymlinks: null

• Is there any risk with setting the home directory to writable? #550

The mounts were copied from docker.yaml

The other directory should work, possibly some issue when running docker as root ?

I thought that fuse.conf had user_allow_other, but maybe it also needs allow_other.

[afbjorklund]

anders@lima-kind:/home/anders/lima$ mkdir /tmp/lima/foo
anders@lima-kind:/home/anders/lima$ sudo -i
root@lima-kind:~# mkdir /tmp/lima/bar
root@lima-kind:~# exit
logout
anders@lima-kind:/home/anders/lima$ docker run -it -v /tmp/lima/baz:/mnt busybox
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
anders@lima-kind:/home/anders/lima$ newgrp docker
anders@lima-kind:/home/anders/lima$ docker run -it -v /tmp/lima/baz:/mnt busybox
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
5cc84ad355aa: Pull complete 
Digest: sha256:5acba83a746c7608ed544dc1533b87c737a0b0fb730301639a0179f9344b1678
Status: Downloaded newer image for busybox:latest
docker: Error response from daemon: error while creating mount source path '/tmp/lima/baz': chown /tmp/lima/baz: permission denied.
ERRO[0004] error waiting for container: context canceled 

[cmoulliard]

I thought that fuse.conf had user_allow_other, but maybe it also needs allow_other.

Where can we set such values (lima yaml file, ...) ?

[afbjorklund]

/etc/fuse.conf, but it was not it

[afbjorklund]

I see this in the docker logs:

level=warning msg="path in container /dev/fuse already exists in privileged mode"

And it works, when mounting /dev/fuse device.

Without it, the mount point must already exist on the host before starting container.

[afbjorklund]

I never mounted Fuse.

sshfs uses fusermount

[cmoulliard]

Sorry but I still don't yet understand what we should do to fix the issues.

[afbjorklund]

Did you create the mountpoints (that you want to use as volumes in docker), with the same ownership as in the container ?

If the directory already exists, I didn't get the same error when trying to chown. It, in turn, seems related to the sshfs used.

[cmoulliard]

Did you create the mountpoints (that you want to use as volumes in docker), with the same ownership as in the container ?

That should be done by lima. We dont have to do that on mac using docker desktop

[afbjorklund]

It is a workaround, lima uses rootless docker so it doesn't have to chown anything (since it is already owned by the same user)