Hi,

I am using the Sourcehut build server to create a docker image, which I am then saving as a tar file using: 

docker save xxx_image_test > xxx_image_test_0.1.0.tar

The build is failing on the save command with:  write /dev/stdout: no space left on device

When I ssh onto the linux image there is 40GB of space, the tar file is around 5GB.  I can manually run the docker save command on the image.

Any help much appreciated, I'm new to docker and sourcehut builds.

Thanks
Sarah

On 7/5/23 11:45, Sarah Fairbairn wrote:
> The build is failing on the save command with:  write /dev/stdout: no space left on device

Given that error message, and this being docker, let me make a wild 
guess: /dev/stdout is typically a link to /proc/self/fd/1, and both /dev 
and /proc have different filesystems mounted on them (a tmpfs and procfs 
respectively). A procfs isn't really writable so most likely /dev/stdout 
didn't exist or wasn't a link, causing the file to be actually written 
into the tmpfs (which then filled up).

Can you put a `ls -l /dev/stdout` in your build.yml before the docker 
save command and check/paste the output?

Conrad Hoffmann <ch@bitfehler.net> writes:

> On 7/5/23 11:45, Sarah Fairbairn wrote:
>> The build is failing on the save command with:  write 
>> /dev/stdout: no space left on device
>
> Given that error message, and this being docker, let me make a 
> wild guess:
> /dev/stdout is typically a link to /proc/self/fd/1, and both 
> /dev and /proc have
> different filesystems mounted on them (a tmpfs and procfs 
> respectively). A
> procfs isn't really writable so most likely /dev/stdout didn't 
> exist or wasn't a
> link, causing the file to be actually written into the tmpfs 
> (which then filled
> up).
>
> Can you put a `ls -l /dev/stdout` in your build.yml before the 
> docker save
> command and check/paste the output?

I am seeing out of disk space errors now too, has the disk space 
amount changed on the build hosts recently?

-- 
  Malcolm Matalka
  Abiogenesis Computer Systems Lab