Skip to content

CI: Failure because we use the fork's docker image

looking at the CI jobs, we can see that the docker image gets pulled from the fork s repo registry:

Using Docker executor with image registry.freedesktop.org/makohoek/drm-hwcomposer:latest ...

See: https://gitlab.freedesktop.org/mdnavare/drm-hwcomposer/-/jobs/64922968

This is problematic because forks don't necessarily have this docker image build.

In my case, I have an outdated image and in order to update it, I must run:

$ docker build -f .ci/Dockerfile -t registry.freedesktop.org/makohoek/drm-hwcomposer:latest .
$ TOKEN=<my_token>
$ echo "$TOKEN" | docker login registry.freedesktop.org/makohoek/drm-hwcomposer -u makohoek --password-stdin
$ docker push registry.freedesktop.org/makohoek/drm-hwcomposer:latest

Resolve this by using the upstream container image whenever no Dockerfile changes are made.