[GH-ISSUE #178] Docker full image is running out of space #120

Closed
opened 2026-03-01 21:40:21 +03:00 by kerem · 3 comments
Owner

Originally created by @Brantone on GitHub (Apr 1, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/178

Tried a couple times but keeps failing on different commands:

$ docker pull nektos/act-environments-ubuntu:18.04-full
18.04-full: Pulling from nektos/act-environments-ubuntu
5c939e3a4d10: Already exists 
c63719cdbe7a: Already exists 
19a861ea6baf: Already exists 
651c9d2d6c4f: Already exists 
8dd387d4677b: Already exists 
2277daa6bda3: Already exists 
44122f010d2c: Already exists 
27df41a4b327: Already exists 
6ff41af36e89: Extracting [==================================================>]   11.9GB/11.9GB
failed to register layer: Error processing tar file(exit status 1): write /usr/local/lib/android/sdk/build-tools/25.0.2/i686-linux-android-ld: no space left on device
Originally created by @Brantone on GitHub (Apr 1, 2020). Original GitHub issue: https://github.com/nektos/act/issues/178 Tried a couple times but keeps failing on different commands: ``` $ docker pull nektos/act-environments-ubuntu:18.04-full 18.04-full: Pulling from nektos/act-environments-ubuntu 5c939e3a4d10: Already exists c63719cdbe7a: Already exists 19a861ea6baf: Already exists 651c9d2d6c4f: Already exists 8dd387d4677b: Already exists 2277daa6bda3: Already exists 44122f010d2c: Already exists 27df41a4b327: Already exists 6ff41af36e89: Extracting [==================================================>] 11.9GB/11.9GB failed to register layer: Error processing tar file(exit status 1): write /usr/local/lib/android/sdk/build-tools/25.0.2/i686-linux-android-ld: no space left on device ```
kerem 2026-03-01 21:40:21 +03:00
Author
Owner

@mced commented on GitHub (Apr 1, 2020):

@Brantone looks like the directory which contains your docker images is full.
Can you validate this by checking the output of df -h?

<!-- gh-comment-id:607084699 --> @mced commented on GitHub (Apr 1, 2020): @Brantone looks like the directory which contains your docker images is full. Can you validate this by checking the output of `df -h`?
Author
Owner

@Brantone commented on GitHub (Apr 1, 2020):

$ df -h
Filesystem      Size   Used  Avail Capacity iused      ifree %iused  Mounted on
/dev/disk1s1   932Gi   10Gi  392Gi     3%  484286 9767493874    0%   /
devfs          337Ki  337Ki    0Bi   100%    1164          0  100%   /dev
/dev/disk1s2   932Gi  526Gi  392Gi    58% 4039602 9763938558    0%   /System/Volumes/Data
/dev/disk1s5   932Gi  3.0Gi  392Gi     1%       3 9767978157    0%   /private/var/vm
map auto_home    0Bi    0Bi    0Bi   100%       0          0  100%   /System/Volumes/Data/home
/dev/disk1s4   932Gi  502Mi  392Gi     1%      39 9767978121    0%   /Volumes/Recovery

Running macOS 10.15.3 ; Docker 19.03.8.
Older Docker posts suggest image was failing to dynamically expand; however, all suggested attempts proved useless. Even doing prune didn't do anything; however, beginning to suspect one of the attempts at running matrix job might be a catalyst.
Will try digging again in the morning.

<!-- gh-comment-id:607098192 --> @Brantone commented on GitHub (Apr 1, 2020): ``` $ df -h Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/disk1s1 932Gi 10Gi 392Gi 3% 484286 9767493874 0% / devfs 337Ki 337Ki 0Bi 100% 1164 0 100% /dev /dev/disk1s2 932Gi 526Gi 392Gi 58% 4039602 9763938558 0% /System/Volumes/Data /dev/disk1s5 932Gi 3.0Gi 392Gi 1% 3 9767978157 0% /private/var/vm map auto_home 0Bi 0Bi 0Bi 100% 0 0 100% /System/Volumes/Data/home /dev/disk1s4 932Gi 502Mi 392Gi 1% 39 9767978121 0% /Volumes/Recovery ``` Running macOS 10.15.3 ; Docker 19.03.8. Older Docker posts suggest image was failing to dynamically expand; however, all suggested attempts proved useless. Even doing prune didn't do anything; however, beginning to suspect one of the attempts at running matrix job might be a catalyst. Will try digging again in the morning.
Author
Owner

@github-actions[bot] commented on GitHub (Jun 16, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

<!-- gh-comment-id:644455169 --> @github-actions[bot] commented on GitHub (Jun 16, 2020): Issue is stale and will be closed in 7 days unless there is new activity
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#120
No description provided.