tests
tests copied to clipboard
kata-containers
The `setup.sh` script occasionally fails with Rust 1.54 with "fatal: unable to fork"
The following run errors were found while developing #4261:
This happens after the following:
Processing triggers for libc-bin (2.31-0ubuntu9) ...
INFO: Create symlink to /tmp in /var to create private temporal directories with systemd
INFO: Install tmp.mount in ./etc/systemd/system
INFO: Create /rootfs/etc
I am ubuntu
INFO: Configure chrony file /rootfs/etc/chrony/chrony.conf
/kata-containers/tools/osbuilder/rootfs-builder/rootfs.sh: line 561: rustup: command not found
/home/kata/go/src/github.com/kata-containers/tests /
Your branch is up to date with 'origin/main'.
Already on 'main'
A good run shows:
Already up to date.
/
/home/kata/go/src/github.com/kata-containers/tests /
Install rust 1.54.0
info: downloading installer
info: profile set to 'default'
info: default host triple is x86_64-unknown-linux-gnu
warning: Updating existing toolchain, profile choice will be ignored
info: syncing channel updates for '1.54.0-x86_64-unknown-linux-gnu'
info: default toolchain set to '1.54.0-x86_64-unknown-linux-gnu'
1.54.0-x86_64-unknown-linux-gnu unchanged - rustc 1.54.0 (a178d0322 2021-07-26)
Rust is installed now. Great!
A bad run shows:
error: cannot run ssh: No such file or directory
fatal: unable to fork
Failed at 566: bash ${script_dir}/../../../ci/install_rust.sh ${RUST_VERSION}
make: *** [Makefile:93: /home/kata/go/src/github.com/kata-containers/kata-containers/tools/osbuilder/.ubuntu_rootfs.done] Error 1
[install_kata_image.sh:50] ERROR: sudo -E USE_DOCKER= DISTRO=ubuntu make -e image
[install_kata.sh:22] ERROR: .ci/install_kata_image.sh
I have a machine where this happens consistently in a libvirt VM. The vagrant VM does not seem to have any problem, but I have not reinstalled that VM for a long time.
I never saw that error before. The fact it cannot fork a process, makes me believe it is a constraint in your VM.
