vfs storage driver does not work on NFS #45417
Description
Description
vfs storage driver does not work on NFS.
A simple 'docker run -it alpine' results in the following error:
docker: Error response from daemon: operation not supported.
level=error msg="Handler for POST /v1.42/containers/create returned error: operation not supported"
Using strace and what I got is:
lgetxattr("/var/lib/docker/vfs/dir/a93d6acc41f0fddc597f35fa1fb0b1c1b79c8ab04000570473cd15da20131cf3", "
security.capability", 0xc000f3b200, 128) = -1 EOPNOTSUPP (Operation not supported)
This means it's trying to get extended security attributes but the underlying NFS does not support it.
Is this expected or is this a bug?
Reproduce
docker run -it alpine
Expected behavior
docker run succeeds
docker version
# docker version
Client:
Version: 20.10.21-ce
API version: 1.41
Go version: go1.20.1
Git commit: baeda1f82a
Built: Thu Apr 27 02:36:59 2023
OS/Arch: linux/amd64
Context: default
Experimental: true
Server:
Engine:
Version: 20.10.21-ce
API version: 1.41 (minimum version 1.12)
Go version: go1.20.1
Git commit: 4ed81ac0e2-unsupported
Built: Wed Nov 9 03:13:48 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.7.0-11-g6ea9bc57f.m
GitCommit: 6ea9bc57f97cd6bdd62afe8c8295706de36afd51.m
runc:
Version: 1.1.5+dev
GitCommit: v1.1.5-1-g17a2d451-dirty
docker-init:
Version: 0.19.0
GitCommit: b9f42a0-dirtydocker info
# docker info
Client:
Context: default
Debug Mode: false
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 20.10.21-ce
Storage Driver: vfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 6ea9bc57f97cd6bdd62afe8c8295706de36afd51.m
runc version: v1.1.5-1-g17a2d451-dirty
init version: b9f42a0-dirty
Kernel Version: 5.15.103-yocto-standard
Operating System: Poky (Yocto Project Reference Distro) 4.2 (mickledore)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.841GiB
Name: qemux86-64
ID: PRTU:AZVE:RYAU:RIET:2XA2:AEPF:RJAZ:XFVO:XZEC:SOS4:WH2P:E776
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: falseAdditional Info
The above 'docker version' & 'docker info' output are about 20.10.21, but I want to clarify that this issue has been is still there on current docker.
On docker 23.0.2, we got this problem.
On docker 20.10.21, we got this problem.
On docker 20.10.17, there's no such problem.