search

indilib / indi-3rdparty

INDI 3rd Party drivers repository
https://www.indilib.org/devices.html
GNU Lesser General Public License v2.1
124 stars 208 forks source link

No merge please - Testing Ubuntu/Fedora build. #864

Closed TallFurryMan closed 9 months ago

TallFurryMan commented 9 months ago

This MRis here to test the build issue on Fedora and Debian. No merge please.

TallFurryMan commented 9 months ago

The digest used by the Ubuntu build is: Digest: sha256:3ddc29f3d16d79c2a3180d421881233eb540b5248e1c9cfb78239654ea74f0d4

The digest returned by docker manifest inspect for ghcri.io/indilib/ubuntu:latest is: "digest": "sha256:1edf3f189b8e223067c7daf81949063658a101ebda442b564228402c3ec1d293"

The digest generated by the last Github Action for ubuntu:latest is: sha256:3ddc29f3d16d79c2a3180d421881233eb540b5248e1c9cfb78239654ea74f0d4

I don't understand why the build won't pick ubuntu:latest as we see it from outside. I'll open a support ticket.

That said, even if the image is not the expected one, it is recent enough that builds succeed.

TallFurryMan commented 9 months ago

So the problem lies also with docker manifest inspect, which does not work in all situations. The right tool for inspection is in package docker-buildx:

$ docker buildx imagetools inspect ghcr.io/indilib/ubuntu:latest
Name:      ghcr.io/indilib/ubuntu:latest
MediaType: application/vnd.docker.distribution.manifest.v2+json
Digest:    sha256:3ddc29f3d16d79c2a3180d421881233eb540b5248e1c9cfb78239654ea74f0d4

Here the digest is OK. That does not explain why there was a discrepancy in images at some point, as the Github Action building one image would not provide the same digest as the build executed afterwards. I suppose it is sufficient for now to say there is a non-deterministic delay between the image build and its use in MR checks.