A.I.
The latest `/var/lib/docker-root/start.sh` is; ``` [docker@docker-root ~]$ cat /var/lib/docker-root/start.sh #!/bin/sh NFS_ROOT=$(cat /proc/cmdline | sed -n 's/^.*docker-root.nfsroot="\([^"]\+\)".*$/\1/p') SHARED_FOLDER=$(cat /proc/cmdline | sed -n 's/^.*docker-root.shared_folder="\([^"]\+\)".*$/\1/p') : ${SHARED_FOLDER:="${NFS_ROOT}"} VIRTFS_UNAME=$(cat /proc/cmdline | sed -n 's/^.*docker-root.virtfs_uname=\([^...
@if-kenn I add some instructions to upgrade `start.sh` in the `docker-root-data.img`. This will fix some errors related to volumes on migration, but others might be caused by Docker. Thanks. Note:...
That's docker-root-data.img v1.1.2 which came with docker-root-xhyve v1.2.11. https://github.com/ailispaw/docker-root-xhyve/releases/tag/v1.1.2 So you have not updated docker-root-data.img util now, because `make upgrade` doesn't update the data volume. I updated the instruction for...
Try `make halt` and `make up` again, after following the upgrade instruction.
And check your `/etc/exports`.
Hmm. Could you make sure the `/var/lib/docker-root/start.sh` is up to date?
Hmm. That looks good... Do you use any security preference in Mac OSX? And nfsd in your Mac OSX is running?
Hmm. I will figure it out.
Please remove `,udp,actimeo=1` at the mount line in start.sh. I'm still investigating.
I can mount it in both cases (with/without `,udp,actimeo=1`), but it might be a workaround for you.