74 added the oci-rootfs.sh script which automatically selects podman instead of docker when it is available on the system running the oci-rootfs.sh script. This PR fixes the following command in that script:
Before I made the change in this PR, this command would fail on my computer with the following output:
Trying to pull docker.io/amd64/alpine:latest...
Getting image source signatures
Copying blob 4abcf2066143 skipped: already exists
Copying config 05455a0888 done |
Writing manifest to image destination
05455a08881ea9cf0e752bc48e61bbd71a34c029bb13df01e40e3e70e0d007bd
Using temporary container 2090805
fetch https://dl-cdn.alpinelinux.org/alpine/v3.19/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.19/community/x86_64/APKINDEX.tar.gz
(1/6) Installing libgcc (13.2.1_git20231014-r0)
(2/6) Installing libstdc++ (13.2.1_git20231014-r0)
(3/6) Installing gc (8.2.4-r1)
(4/6) Installing ncurses-terminfo-base (6.4_p20231125-r0)
(5/6) Installing libncursesw (6.4_p20231125-r0)
(6/6) Installing w3m (0.5.3.20230718-r1)
Executing busybox-1.36.1-r15.trigger
OK: 12 MiB in 21 packages
Error: no container with name or ID "2090805" found: no such container
When I had turned on debugging output (by changing the shebang line from #!/usr/bin/env bash to #!/usr/bin/env -S bash -eux), I saw the following output:
After making the fix in this PR, I also attempted to use oci-rootfs.sh on GitHub Actions. The version of Podman or Docker available in the ubuntu-22.04 runner appeared to be too old, resulting in this error in the following output (full CI logs here):
This error was easily resolved by upgrading to the ubuntu-24.04 runner (refer to the GitHub Actions CI log here, and the associated commit here, and the context for that change here). To conclude, this confirms for me that the script, [even] after the changes made in this PR, can work as expected on GitHub Actions (as long as we use the ubuntu-24.04 runner).
74 added the
oci-rootfs.sh
script which automatically selectspodman
instead ofdocker
when it is available on the system running theoci-rootfs.sh
script. This PR fixes the following command in that script:https://github.com/flatcar/sysext-bakery/blob/11280db5e80530505857385af088525d3be1675a/oci-rootfs.sh#L50 which assumes the use of
docker
, even whenpodman
is used for all other commands, and which had resulted in the script quitting with an error whenpodman
is selected instead ofdocker
for https://github.com/flatcar/sysext-bakery/blob/11280db5e80530505857385af088525d3be1675a/oci-rootfs.sh#L53Testing done
"it works on my machine"
On my computer (which is running the https://github.com/ublue-os/bluefin/pkgs/container/aurora-dx custom Fedora OS image), I attempted to run the following command:
Before I made the change in this PR, this command would fail on my computer with the following output:
When I had turned on debugging output (by changing the shebang line from
#!/usr/bin/env bash
to#!/usr/bin/env -S bash -eux
), I saw the following output:After the change in this PR, I no longer have errors on my computer when running the same command:
"it works on GitHub Actions's machines"
After making the fix in this PR, I also attempted to use
oci-rootfs.sh
on GitHub Actions. The version of Podman or Docker available in the ubuntu-22.04 runner appeared to be too old, resulting in this error in the following output (full CI logs here):This error was easily resolved by upgrading to the ubuntu-24.04 runner (refer to the GitHub Actions CI log here, and the associated commit here, and the context for that change here). To conclude, this confirms for me that the script, [even] after the changes made in this PR, can work as expected on GitHub Actions (as long as we use the ubuntu-24.04 runner).