Eric Hough

Thanks for your question. Could you tell us a little more about your use case? Are you looking to run this container on a dedicated HTPC running macOS? or Windows?...

I *think* I found a solution. It's a bit hacky due to the nature of Docker for Mac's architecture, and I haven't tested this since don't have immediate access to...

Update - I was able to test this procedure on mac OS Mojave. It fixes the `ERROR: nfs module is not loaded` error, but now `exportfs` is complaining: `exportfs: Warning:...

Another update: I was able to make further progress by 1. Ensuring that any bind-mounted directories where present in the "File Sharing" preferences area. 1. Adding the `fsid` parameter to...

@HumbleSpirit could you pass along your full `docker run` command (or `docker-compose.yml`, etc.)? Your invocation *should not* have raised hat error.

@HumbleSpirit thank you. I'm assuming that `$(pwd)` is `/Users/admin/Downloads/pxe_docker`. In that case, > `-v "$(pwd)/nfsroot/client1":/nfs` means that `/Users/admin/Downloads/pxe_docker/nfsroot/client1` will be available inside the container at `/nfs/nfsroot/client1`. So you simply need...

Taking a look now. It'll take me a moment to digest your issue. Thanks for posting your debug logs - that's super helpful! Stand by.

Couple of clarifying questions: 1. Does it matter to you if you use NFSv3 or NFSv4? The performance difference, in my experience, is negligible. NFSv3 tends to be easier to...

Hmm, that error message is certainly the one that usually accompanies AppArmor interference. But what's also weird is that even though `NFS_LOG_LEVEL` is set to `DEBUG`, we're not seeing the...

What's the output of: `rpcinfo 127.0.11.20` and (if you have netcat installed) `nc -z 127.0.11.20 2049 && echo open || echo closed` I'm just wondering if we're dealing with a...