Closed uuf6429 closed 12 months ago
full-latest
is not built in this repository even if docs are suggesting otherwise.
full-latest
seem to be dead, this repo still get's unregular updates if something breaks.
full-latest
was built from https://github.com/catthehacker/virtual-environments-fork
and it's not updated since long time ago because it requires a lot of effort to adapt the GitHub runner images to work in container
@catthehacker Do you agree pushing tar layers of GitHub Hosted Runners to full-latest?
https://github.com/ChristopherHX/runner-image-blobs, I made a script to stream upload layers to the docker registry. So just copy the latest tag to the outdated tag, maybe using skopeo
This bumps node to 18 and is a 99% clone of the official image.
A single tar.gz had 20GiB with gzip -9 and extracted it's bigger.
I also made medium images from it with 5GiB or less in download. (x86_64 only)
Do you agree pushing tar layers of GitHub Hosted Runners to full-latest?
Sure, thank you for all your work 🎉
Replacing images in progress...........
Anyone who want to go back in history to the old ubuntu 20.04/latest image here the fully qualified tags
catthehacker/ubuntu@sha256:598b616a8c7ce86d98ee63871cec532f4ff645125b563a8798f2ae1c98928ec7
ghcr.io/catthehacker/ubuntu@sha256:598b616a8c7ce86d98ee63871cec532f4ff645125b563a8798f2ae1c98928ec7
They may become invalid in some months, due to garbage collection. The ghcr version is expected to last longer.
Despite #47, images are still using node14, which among other things, is causing https://github.com/nektos/act/issues/1681.
I also tried
docker run --rm --entrypoint node catthehacker/ubuntu:full-latest -v
with the same outcome.Off topic: any idea why
docker run --rm catthehacker/ubuntu:full-latest node -v
doesn't work? I had the impression that the next argument after the docker image is taken as the entrypoint, and everything else as cmd arguments?