mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #60] Getting "no space left on device" errors #35
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#35
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sarahs on GitHub (Apr 30, 2019).
Original GitHub issue: https://github.com/nektos/act/issues/60
Thanks for this project @nektos, it's a super useful tool.
It worked great for me for a while, but now I'm getting
Unhandled rejection Error: ENOSPC: no space left on deviceerrors when mynpm ciaction runs.I added
df -hto my workflow file to see what's going on, and it shows I've used 100% of space in/github/home:But doing an
ls -ain that dir shows it's empty. I've cleared every cache I can think of, removednode_modulesbefore install, and randocker system prune -af, but still get the error.I asked the Actions folks and they think it might be related to
act, since I only get the error locally and not when running the workflow in a PR.Thanks for any advice!
@thedarkwriter commented on GitHub (Jun 6, 2019):
I can confirm the behavior with NPM with Act and what is interesting is follow on installations work no errors talking about no space left on device:
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion" # This loads nvm bash_completion
Downloading and installing node v10.14.1...
Downloading https://nodejs.org/dist/v10.14.1/node-v10.14.1-linux-x64.tar.xz...
######################################################################## 100.0%
Computing checksum with sha256sum
Checksums matched!
tar: bin/node: Wrote only 6656 of 10240 bytes
tar: lib/node_modules/npm/appveyor.yml: Cannot write: No space left on device
tar: lib/node_modules/npm/.travis.yml: Cannot write: No space left on device
tar: lib/node_modules/npm/changelogs/CHANGELOG-3.md: Cannot write: No space left on device
...
then
Downloading https://nodejs.org/dist/v10.14.1/node-v10.14.1.tar.xz...
################### 26.5%
curl: (23) Failed writing body (265 != 16366)
Binary download from https://nodejs.org/dist/v10.14.1/node-v10.14.1.tar.xz failed, trying source.
grep: /github/home/.nvm/.cache/src/node-v10.14.1/node-v10.14.1.tar.xz: No such file or directory
Provided file to checksum does not exist.
2019-06-06-15-205299500 Installing GCP SDK ...
deb http://packages.cloud.google.com/apt cloud-sdk-bionic main
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1326 100 1326 0 0 7325 0 --:--:-- --:--:-- --:--:-- 7325
OK
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://packages.cloud.google.com/apt cloud-sdk-bionic InRelease [6372 B]
Get:3 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:5 http://packages.cloud.google.com/apt cloud-sdk-bionic/main amd64 Packages [75.3 kB]
Hit:6 http://archive.ubuntu.com/ubuntu bionic-backports InRe
Also, it looks like the /home/github is at 100% from the very start
root@ba5ca325fe7e:/github/workspace# df -h
Filesystem Size Used Avail Use% Mounted on
overlay 59G 9.9G 46G 18% /
tmpfs 64M 0 64M 0% /dev
tmpfs 1000M 0 1000M 0% /sys/fs/cgroup
osxfs 234G 145G 82G 64% /github/workspace
overlay 1000M 1000M 0 100% /github/home
/dev/sda1 59G 9.9G 46G 18% /etc/hosts
shm 64M 0 64M 0% /dev/shm
tmpfs 200M 808K 200M 1% /run/docker.sock
tmpfs 1000M 0 1000M 0% /proc/acpi
tmpfs 1000M 0 1000M 0% /sys/firmware
@thedarkwriter commented on GitHub (Jun 6, 2019):
Looks like anything that unpacks or copies to /github/home will hit that error
cp: error writing './static/app/account/views/user-reviews.directive.html': No space left on device
@maxheld83 commented on GitHub (Jun 7, 2019):
yup, same problem.
The only fix I got is to go nuclear:
rm -rf ~/Library/Containers/com.docker.docker/Data/vms/0/Docker.qcow2Warning: this is a destructive action; be careful@thedarkwriter commented on GitHub (Jun 7, 2019):
@maxheld83 I was considering remapping home on the fly away from /github/home (though I know that's shimming away from how actions actually work). If that doesn't work I will likely try your nuke.
@cplee commented on GitHub (Feb 25, 2020):
Latest release of act (
0.2.2) is using docker volumes rather than bind mounts.@ureciocais commented on GitHub (Jan 10, 2023):
Hi, I'm getting "no space left on device" on v0.2.35
Using this image: catthehacker/ubuntu:full-latest
@liudmylaru commented on GitHub (Jan 23, 2023):
hi! @ureciocais according message above from cplee act >= 0.2.2 is using volumes, you can try clean that space (used by volumes) with this command "docker volume prune --force". For me - it helped. I am using act v0.2.40, and image "nektos/act-environments-ubuntu:18.04". Had the same error.
@timastoicguy commented on GitHub (Oct 11, 2024):
✅ I solved the problem on my Macbook M3 Pro
My configuration:
act version: 0.2.68docker version: 27.2.0I fixed this problem by adding more spaces to Docker
Here is how I did that:
Go to Docker Desktop -> Settings -> Resources -> Change virtual disk limit to 200GB (previously I used 64GB)
@bilogic commented on GitHub (Dec 16, 2024):
Any idea how to do this on the CLI?