On Tue, Jul 22, 2025 at 12:39 AM Dmitry Kazakov <dimul...@gmail.com> wrote:
> > >Trying to run a Docker image inside a VM based CI image would be an awful > hack and while more than doable would be difficult to support and debug, > gives up basically all the benefits of being VM based, and would be slower > in general as well as more expensive for us to run resource wise. It's not > something i'm going to be particularly happy about you running. > > <...> it is possible for the CI system to produce both a VM image as > well as a Docker image > > Well, we need an exactly the same environment (esp. package-wise) in a > local docker image and in VM. How can we guarantee that? Where are the base > Ubuntu VM images pulled from? How do they correlate to the base docker > images? > The VM and Docker images, assuming they're built at the same time, should be practically identical for all intents and purposes. With the exception of FreeBSD, all VM images built and used on the CI system have the original underlying image sourced from the distribution itself. See the BASE_IMAGE variable in https://invent.kde.org/sysadmin/ci-images/-/blob/master/.gitlab-ci.yml?ref_type=heads for details on specifics. As part of our image build process we update the image to the latest system packages anyway, so when the underlying image was last built by the distribution does not particularly matter. As for what is in it, the Docker images by their very nature will be more stripped down, however i'd expect that the VM images will be the same as the Docker images, except they'll have system level components like the kernel, systemd, etc. added in which aren't needed in a Docker context. > > >> For non-Linux OSes, only VM based images are supported now and there is >> no possibility to build Docker/Podman images for them. >> > > For non-Linux OSes it is somewhat fine, even though we use docker for > Android as well. > > > >> As a starting point, has Krita transitioned to the 2204 based images? >> > > Yes, I wanted to make a MR to delete *-2004 images, but waited till you > lift the docker-image-freeze. > I'd suggest you double check the Krita CI setup, when doing the Windows one I noticed an old image URL being used. build-tools/ci-scripts/android.yml: image: invent-registry. kde.org/sysadmin/ci-images/krita-android-builder-sdk34-2204:latest build-tools/ci-scripts/android.yml: image: invent-registry. kde.org/sysadmin/ci-images/krita-android-builder-sdk34-2204:latest build-tools/ci-scripts/cppcheck.yml: image: invent-registry. kde.org/sysadmin/ci-images/krita-appimage-builder:latest build-tools/ci-scripts/linux.yml: image: invent-registry. kde.org/sysadmin/ci-images/krita-appimage-builder-2204:latest Cheers, Ben
