Skip to content

Always pull :latest tag images #26

@artem-zinnatullin

Description

@artem-zinnatullin

Hi @ligfx!

Many thanks to you for this wonderful project, it works much faster than kind load docker-image and k3d image import for big set of images!

One thing we just found is that ligfx/k3d-registry-dockerd:v0.10 doesn't seem to respect :latest tags on images, we use k3d for local development and integration test run on k3d triggers rebuild of microservice images in the monorepo.

We tag dev-built images with :latest expecting them to always be pulled-through by both k3d/k3s and ligfx/k3d-registry-dockerd:v0.10, but new :latest image is not getting resolved in the registry once it's cached.

For now I came up with this workaround:

docker exec k3d-integration-test-0-registry sh -c 'rm -rf /cache/privateregistry.xyz.com%2F*/indexes/latest'

This deletes the indexes of our :latest images in the running container(s) of ligfx/k3d-registry-dockerd:v0.10, which forces the registry to re-pull from Docker when k3s requests it and we get the correct behavior!
It even preserves the blobs for faster reuse lol.

But ideally k3d-registry-dockerd should support :latest behavior automatically :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions