nixos-docker-sd-image-builder: Error while copying store paths to image

Hi!

This project seems very promising and your blog post is very nice, so thank you!

While trying to make it work as-is (I just updated the SSH key), everything seems to work fine until I get the following error:

build-nixos_1   | building '/nix/store/j6w1im36k9dgn44clb3f8bh43da9y6cy-ext4-fs.img.zst.drv'...
build-nixos_1   | Creating an EXT4 image of 2854793216 bytes (numInodes=95866, numDataBlocks=505239)
build-nixos_1   | mke2fs 1.45.5 (07-Jan-2020)
build-nixos_1   | Discarding device blocks: done
build-nixos_1   | Creating filesystem with 696971 4k blocks and 174592 inodes
build-nixos_1   | Filesystem UUID: 44444444-4444-4444-8888-888888888888
build-nixos_1   | Superblock backups stored on blocks:
build-nixos_1   |         32768, 98304, 163840, 229376, 294912
build-nixos_1   |
build-nixos_1   | Allocating group tables: done
build-nixos_1   | Writing inode tables: done
build-nixos_1   | Creating journal (16384 blocks): done
build-nixos_1   | Writing superblocks and filesystem accounting information: done
build-nixos_1   |
build-nixos_1   | copying store paths to image...
build-nixos_1   | /nix/store/690a5swp0j228wx5snj3izs0zayd967l-stdenv-linux/setup: line 1299:  6752 Killed                  cptofs -t ext4 -i $img $storePaths /nix/store/
build-nixos_1   | builder for '/nix/store/j6w1im36k9dgn44clb3f8bh43da9y6cy-ext4-fs.img.zst.drv' failed with exit code 137
build-nixos_1   | cannot build derivation '/nix/store/vxca84dr6k2xqsg78wdx2qlszm8v9kz5-nixos-sd-image-20.03post-git-aarch64-linux.img.drv': 1 dependencies couldn't be built

I’m using the latest Docker Toolbox on Windows 10:

Docker version 19.03.1, build 74b1e89e8a
docker-compose version 1.24.1, build 4667896b

I tried to put 2 GB of RAM (instead of 1) in the VM (Docker Toolbox runs Docker inside a VirtualBox VM), but nothing changed.

Any idea of what could be wrong or how to investigate?

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 20 (11 by maintainers)

Commits related to this issue

Most upvoted comments

Just to say I encountered this today, and just bumping my Docker memory from 2 to 12GB worked nicely. Many thanks to @Robertof and @SuperCipher!

Hey @ccamrobertson – as promised, I’ve played around with the various configurations and made this repo (hopefully) RPi 4 compatible! 🎉

However, I was not able to reproduce your issue – i.e., even using the config you gave me verbatim the build succeeded at the first try. Could there be something weird on the host OS, e.g. strange limits/extremely out-of-date Docker/not enough disk space? Note that it should also work on macOS as in theory Docker just virtualizes a Linux distro to work on macOS.

Feel free to pull this repo, change rpi3 to rpi4 in config/sd-image.nix and give it another shot. Note that I’ve added first-party support to the patch which removes cptofs, so you should only need to change the flag in docker/docker-compose.yml.

Thanks! Roberto

Thanks! I don’t see any issue with your configs. I’ll experiment with it this evening and let you know!