colima/docker "no space left on device"
Closed this issue · 1 comments
speedmax commented
I am getting "no space left on device" when I run docker compose --profile current up -d
, it reaches around 50/67 stages and sometime it gets to 65/57 step.
Docker Root Dir has updated to a 4TB external NVME drive, and colima/docker configured 3TB storage.
colima list
PROFILE STATUS ARCH CPUS MEMORY DISK RUNTIME ADDRESS
default Running aarch64 4 16GiB 2.93TiB docker
Docker info
Client: Docker Engine - Community
Version: 24.0.4
Context: colima
Debug Mode: false
Plugins:
compose: Docker Compose (Docker Inc.)
Version: 2.20.2
Path: /Users/decouple/.docker/cli-plugins/docker-compose
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 5
Server Version: 23.0.6
Storage Driver: overlay2
Backing Filesystem: tmpfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
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 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 1fbd70374134b891f97ce19c70b6e50c7b9f4e0d
runc version: 860f061b76bb4fc671f0f9e900f7d80ff93d4eb7
init version:
Security Options:
seccomp
Profile: builtin
Kernel Version: 6.1.29-0-virt
Operating System: Alpine Linux v3.18
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 15.59GiB
Name: colima
ID: 9fbe0001-ae8d-4267-80a3-d0c7d0e54339
Docker Root Dir: /Volumes/data/docker_data
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
speedmax commented
Edited data dir path in envs/mainnet
to use /mnt/data/geth
, that seem to have solved the problem.