You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been giving a try to crun-vm to overcome problems we have with nested containers (CI container running molecule tests) and we use an image based on quay.io/podman/upstream, only adding systemd needed for certain tests.
It seems the image is compatible with crun-vm as it creates it properly (with podman run) but the gitlab preparation script needs to copy the gitlab-runner into the VM before exec-ing the real workload and that fails:
Running with gitlab-runner 17.5.3 (12030cf4)
on gl-runner-podman-02.osci.io t2_D16Jou, system ID: s_cbfa6646c082
Preparing the "custom" executor 00:14
Using Custom executor...
Running in runner-43441658-project-31791330-concurrent-0-8375585513
Login to registry.gitlab.com with CI_REGISTRY_USER
Login Succeeded!
Trying to pull registry.gitlab.com/osci/podman-systemd-container:latest...
Getting image source signatures
Copying blob sha256:1bb9855e1afb4fc53ae94da3fb358868811dacb52e869def9d74ae225d0f6c35
Copying blob sha256:9402150a0e0b7244ce96ca2f7d2ddd29042b8987c5a1c47fe1be6a2ae9eb43c2
Copying blob sha256:5834ff41b0bcc04d91328a62a635de1f699da102d82aaffa20945dc6e3be1a8c
Copying blob sha256:94f43534c2c6d38520040102ef9df87fbb8d0f007277abb0224eb9e14efe2928
Copying blob sha256:e83f3bc2948ac89513f21986e9ec27336afe9805a8ed9767059421dd8ee6ab8f
Copying blob sha256:a97b10dda78d89f54100e53ee5413aa0f4ad4b95f1d6d6587e3ad1d5a13d4393
Copying blob sha256:a2da08455699d2013d3014a1d95a8320b6309e70e143b81af624d0b7dbe2dc07
Copying blob sha256:d8a51423ba93addcb2e8014656cb524200073589bc41da324007c13020239a85
Copying blob sha256:c3a0e61cb4d6199decc85e39b391bdb978fb86138c199aff6153add3509d0cfc
Copying blob sha256:bd7a5cb2d057b8984622e959d2f339a727b98570896891937978f25e5054e40d
Copying blob sha256:40ce70dfa26995362ea261ca9bb210ebdd32a3dedbfbd247ec9996f7f9fe6c9f
Copying config sha256:19a08554818953fa8522731943469838f1d55a3e14ae4b1d97b3ef709c24ff43
Writing manifest to image destination
19a08554818953fa8522731943469838f1d55a3e14ae4b1d97b3ef709c24ff43
291b96464a4c12418089558b70e277e3d3326ede92d24a65bc01a73172f88c7e
Error: 2 errors occurred:
* copying to container: open /proc/658129/ns/mnt: no such file or directory
* copying from host: copier: get: "/usr/bin/gitlab-runner": copying /usr/bin/gitlab-runner: io: read/write on closed pipe
More precisely this command fails: podman cp --pause=false "${RUNNER_BINARY}" "$CONTAINER_ID":/usr/bin/gitlab-runner
Did I make a mistake or is the cp command not supported yet?
Regards.
\_o<
The text was updated successfully, but these errors were encountered:
Quack,
I've been giving a try to crun-vm to overcome problems we have with nested containers (CI container running molecule tests) and we use an image based on
quay.io/podman/upstream
, only adding systemd needed for certain tests.It seems the image is compatible with crun-vm as it creates it properly (with
podman run
) but the gitlab preparation script needs to copy the gitlab-runner into the VM before exec-ing the real workload and that fails:More precisely this command fails:
podman cp --pause=false "${RUNNER_BINARY}" "$CONTAINER_ID":/usr/bin/gitlab-runner
Did I make a mistake or is the cp command not supported yet?
Regards.
\_o<
The text was updated successfully, but these errors were encountered: