Skip to content
This repository was archived by the owner on Oct 6, 2023. It is now read-only.

Commit 2992ceb

Browse files
committed
now supporting NFS v3
1 parent 6e8d56c commit 2992ceb

File tree

2 files changed

+383
-118
lines changed

2 files changed

+383
-118
lines changed

README.md

Lines changed: 25 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -50,15 +50,30 @@ The container requires you to supply it with your desired [NFS exports](https://
5050

5151
Via optional environment variables, you can adjust the server settings to your needs.
5252

53-
| name | default value | description |
54-
|--------------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
55-
| `NFS_VERSION` | `4.2` | Set to `3`, `4`, `4.1`, or `4.2` to fine tune the NFS protocol version. Note that any minor version will also enable any lesser minor versions. e.g. `4.2` will enable versions 4.2, 4.1, 4, **and** 3. |
56-
| `NFS_VERSION_DISABLE_V3` | *not set * | Set to a non-empty value (e.g. `NFS_VERSION_DISABLE_V3=1`) to disable NFS version 3 and run a version-4-only server. This setting is not compatible with `NFS_VERSION=3`. |
57-
| `NFSD_PORT` | `2049` | Set this to any valid port number (`1` - `65535` inclusive) to change `rpc.nfsd`'s listening port. |
58-
| `NFSD_SERVER_THREADS` | *CPU core count* | Set this to a positive integer to control how many server threads `rpc.nfsd` will use. A good minimum is one thread per CPU core, but 4 or 8 threads per core is probably better. |
59-
| `NFS_MOUNTD_PORT` | `32767` | *Not needed for NFS 4*. Set this to any valid port number (`1` - `65535` inclusive) to change `rpc.mountd`'s listening port. |
60-
| `NFS_STATD_IN_PORT` | `32765` | *Not needed for NFS 4*. Set this to any valid port number (`1` - `65535` inclusive) to change `rpc.statd`'s listening port. |
61-
| `NFS_STATD_OUT_PORT` | `32766` | *Not needed for NFS 4*. Set this to any valid port number (`1` - `65535` inclusive) to change `rpc.statd`'s outgoing connection port. |
53+
- **`NFS_VERSION`** (default is `4.2`)
54+
55+
Set to `3`, `4`, `4.1`, or `4.2` to fine tune the NFS protocol version. Note that any minor version will also enable any lesser minor versions. e.g. `4.2` will enable versions 4.2, 4.1, 4, **and** 3. |
56+
57+
- **`NFS_VERSION_DISABLE_V3`** (*not set by default*)
58+
59+
Set to a non-empty value (e.g. `NFS_VERSION_DISABLE_V3=1`) to disable NFS version 3 and run a version-4-only server. This setting is not compatible with `NFS_VERSION=3`. |
60+
61+
- **`NFSD_PORT`** (default is `2049`)
62+
63+
Set this to any valid port number (`1` - `65535` inclusive) to change `rpc.nfsd`'s listening port. |
64+
- **`NFSD_SERVER_THREADS`** (default is *CPU core count*)
65+
66+
Set this to a positive integer to control how many server threads `rpc.nfsd` will use. A good minimum is one thread per CPU core, but 4 or 8 threads per core is probably better. |
67+
68+
- **`NFS_MOUNTD_PORT`** (default is `32767`)
69+
70+
*Not needed for NFS 4*. Set this to any valid port number (`1` - `65535` inclusive) to change `rpc.mountd`'s listening port. |
71+
- **`NFS_STATD_IN_PORT`** (default is `32765`)
72+
73+
*Not needed for NFS 4*. Set this to any valid port number (`1` - `65535` inclusive) to change `rpc.statd`'s listening port. |
74+
- **`NFS_STATD_OUT_PORT`** (default is `32766`)
75+
76+
*Not needed for NFS 4*. Set this to any valid port number (`1` - `65535` inclusive) to change `rpc.statd`'s outgoing connection port.
6277

6378
### Mounting filesystems from a client
6479

@@ -70,7 +85,7 @@ Via optional environment variables, you can adjust the server settings to your n
7085

7186
## Performance considerations
7287

73-
- Running the container with `--network=host` *might* improve network performance by 10% - 20% [[1](https://jtway.co/docker-network-performance-b95bce32b4b9),[2](https://www.percona.com/blog/2016/08/03/testing-docker-multi-host-network-performance/)], though this hasn't been tested.
88+
- Running the container with `--network host` *might* improve network performance by 10% - 20% [[1](https://jtway.co/docker-network-performance-b95bce32b4b9),[2](https://www.percona.com/blog/2016/08/03/testing-docker-multi-host-network-performance/)], though this hasn't been tested.
7489

7590
## Remaining tasks
7691

0 commit comments

Comments
 (0)