-
**What happened**:
```
❥ nomad volume create ./volumes/uptime-v
olume.hcl
Error creating volume: Unexpected response code: 500 (rpc er
ror: 1 error occurred:
* controller create volum…
-
### Description
It might be a bug since i cannot find solution online.
Mounting nfs share directly to a container works when using `docker run` but not when using a compose file with `docker compose`…
-
docker.io/itsthenetwork/nfs-server-alpine:12
-
Recently I installed 'radarr' and 'sonarr' via the truechart helm chart.
Check out this magic:
```
persistence:
sabnzbd-data:
enabled: true
type: nfs
path: /nfs/sabnzbd
…
-
**Platform I'm building on:**
Running a very simple NFS server container on `bottlerocket-aws-k8s-1.25-x86_64-v1.26.1-943d9a41`
Dockerfile:
```
# syntax=docker/dockerfile:1.9
FROM public.ecr…
-
I set up a File Server into the LXC container.
Samba and something else work out of the box. But NFS works just if I open the whole eth0.
I tried opening TCP/UDP ports 111, 2049, 32803, 32769, 875, …
-
Following the README procedure, I found that `stackhpc.nfs` failed at the point of trying to mount NFS because it couldn't resolve the hostname of the Slurm control node:
```
TASK [stackhpc.nfs : mo…
-
docker.io/erichough/nfs-server:2.2.1
-
## Description
With flatcar 3975.2.1 we see very weird behavior of NFS 4.2 where one pod writes a file but a pod on a different host is unable to see the just written file content.
NFS 3 / 4.1 w…
-
On the client, some works for example :
`sudo mount -t nfs -o vers=4.1,sec=sys,port=2050 192.168.0.170:/home/user1 /mnt/nfs_shared`
be correct, but
`sudo mount -t nfs -o vers=4.1,sec=sys,port=2050…