Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-e READ_ONLY vs -e READ_ONLY=true #46

Open
xmontero opened this issue Apr 24, 2021 · 0 comments
Open

-e READ_ONLY vs -e READ_ONLY=true #46

xmontero opened this issue Apr 24, 2021 · 0 comments

Comments

@xmontero
Copy link

xmontero commented Apr 24, 2021

The readme says "Adding -e READ_ONLY will cause the exports file to contain ro instead of rw".

Running this with -e READ_ONLY:

docker run -it --rm --name nfs --privileged -v /tmp:/nfsshare -e SHARED_DIRECTORY=/nfsshare -p 2049:2049 -e READ_ONLY -e SYNC=true itsthenetwork/nfs-server-alpine

it says:

The READ_ONLY environment variable is unset or null, defaulting to 'rw'.
Clients have read/write access.

It says rw when it is supposed to be ro.

Nevertheless with -e READ_ONLY=true like this:

docker run -it --rm --name nfs1 --privileged -v /tmp:/nfsshare -e SHARED_DIRECTORY=/nfsshare -p 2049:2049 -e READ_ONLY=true -e SYNC=true itsthenetwork/nfs-server-alpine

it says:

The READ_ONLY environment variable is set.
Clients will have read-only access.

Should the README be updated? Or am I missing something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant