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
After starting a container, passing host and token as env variables, the NFS access point is not exposed to the host system.
$ docker run -it --privileged -e ONECLIENT_PROVIDER_HOST -e ONECLIENT_ACCESS_TOKEN -v ~/.oneclient_local:/root/.local/share/oneclient onedata/oneclient:17.06.0-beta6
Connecting to provider 'oneprovider.cloud.cnaf.infn.it:5555' using session ID: '7800789129593989533'...
Getting configuration...
Oneclient has been successfully mounted in '/mnt/oneclient'.
but logging in the container one can easily see that NFS is not running, and doesn't start
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
40057641ed30 onedata/oneclient:17.06.0-beta6 "/root/run.sh /mnt..." 2 minutes ago Up 2 minutes eloquent_morse
$ docker exec -it 40057641ed30 bash
root@40057641ed30:/tmp# service nfs-kernel-server status\
nfsd not running
root@40057641ed30:/tmp# service nfs-kernel-server start
* Exporting directories for NFS kernel daemon... [ OK ]
* Starting NFS kernel daemon [ OK ]
root@40057641ed30:/tmp# service nfs-kernel-server status
nfsd not running
as confirmed by trying to mount the remote volume on the host
One can list the content of the mounted directory but its quite slow, much slower than from within the container.
NFS
The command used to list shares, shows nothing:
showmount -e localhost
From within the container we can see that nfs is working:
root@7eb5eced30b4:/tmp# showmount -e 172.17.0.2
Export list for 172.17.0.2:
/mnt/oneclient *
We will continue to investigate, but atm. I'm out of ideas. This feature was developed before native docker for macos was released. With docker running on virtualbox it works well.
After starting a container, passing host and token as env variables, the NFS access point is not exposed to the host system.
but logging in the container one can easily see that NFS is not running, and doesn't start
as confirmed by trying to mount the remote volume on the host
Tested on
17.06.0-beta6
, OSX version 10.12.5, Docker version 17.06.0-ce-mac19 (18663)The text was updated successfully, but these errors were encountered: