Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulling docker image uses too many inodes (no space left on device) #92

Open
intgr opened this issue Jun 13, 2022 · 0 comments
Open

Pulling docker image uses too many inodes (no space left on device) #92

intgr opened this issue Jun 13, 2022 · 0 comments

Comments

@intgr
Copy link

intgr commented Jun 13, 2022

I kept hitting the following error while trying to use this image:

Sending build context to Docker daemon    384kB
Step 1/19 : FROM docker.io/rocm/tensorflow-autobuilds:latest
latest: Pulling from rocm/tensorflow-autobuilds
...
7043cf977ac9: Pull complete 
29590d8cf13a: Extracting [==================================================>]  2.295GB/2.295GB
...
dfdc21b64fe2: Download complete 
failed to register layer: ApplyLayer exit status 1 stdout:  stderr: write /opt/rocm-5.1.0/rocfft/lib/librocfft-device-2.so.0.1.50100: no space left on device

It wasn't obvious that I'm not running out of disk space, but ext4's inode space on my root partition (see df -i).

For anyone else who is stuck with this error, my solution was to move Docker data directory, via /etc/docker/daemon.json:

{
  "data-root": "/home/docker"
}

But it would be preferrable to reduce the inode usage of this image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant