moby: how to solve it? docker: error creating overlay mount to invalid argument
Output of docker version
:
Client:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:23:11 2016
OS/Arch: linux/amd64
Server:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:23:11 2016
OS/Arch: linux/amd64
Output of docker info
:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 1.11.2
Storage Driver: overlay
Backing Filesystem: xfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: host bridge null
Kernel Version: 4.6.2-1.el7.elrepo.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 11.61 GiB
Name: juaby.com
ID: YWHY:CGJF:MVTA:PKZJ:YYOU:52Q6:6Q36:DVY7:HZUP:IGS5:A2GC:BOE6
Docker Root Dir: /export/docker-data
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Additional environment details (AWS, VirtualBox, physical, etc.): cat /etc/redhat-release CentOS Linux release 7.2.1511 (Core)
Steps to reproduce the issue: 1.docker pull registry 2.sudo docker run -d -p 5000:5000 -v /export/docker-data/registry:/tmp/registry registry 3.
Describe the results you received:
docker: Error response from daemon: error creating overlay mount to /export/docker-data/overlay/e86c5ccec4b435b048c3d64753a8dbcedc8655753ee18f256f0800fdedb783c6-init/merged: invalid argument.
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 21 (8 by maintainers)
You can change the storage driver in docker to avoid overlay fs.
As per docker documentation: “To set the storage driver, you can use the --storage-driver flag when starting the Docker daemon manually, or (recommended) set the option in the daemon.json file, which is located in /etc/docker/”
daemon.json content:
{ "storage-driver": "devicemapper" }
change xfs to ext4 and done
I changed my docker storage location to a different drive , because I’m running out of space with my
/
; I did that by udpating/etc/docker/daemon.json
and addI’m able to
docker pull busybox
, but when I rundocker run -it busyobx
I’m getting thedocker: Error response from daemon: error creating overlay mount to /media/bochen2014/NTFSDrive/docker
is it because my external drive of NTFS format?
@bochen2014 Correct, NTFS is not supported with overlayfs, and in a future release (change is already in master), attempting to start docker with ntfs as the backing fs for overlay will be blocked.
The
vfs
driver might work, but is not generally ideal since it will use significantly more space and be much slower at creating containers.@cpuguy83
So what do I do if I want to run docker, don’t have enough space on my / and the only other available partition is NTFS??? Does this mean I can’t use docker??? 😦
@thaJeztah Yeah, I can’t do that since I have to share that partition with files read and created on windows. Is there really no way to run docker in this scenario?