I have a few questions about docker image dep inference. I'm attempting to build a set of 'golden' images that have some deps on other images that i'm also building. in the docs, i see the following:

Inference is also supported for docker_image targets specified in build arguments, 

for example:
ARG BASE_IMAGE=:base
FROM $BASE_IMAGE

In the example, :base is the base image target address specified using a relative path. Pants will provide the built Docker image name for that target as the BASE_IMAGE build arg to the Docker build command.

when running locally, this works fine - the dep is correctly inferred. It seems like

pants package <target image>

tags it in my local docker registry (visible via docker image ls, etc.), but this fails in github actions. this seems more like an issue with Docker / Github actions, as there isn't a local registry running - is that accurate? how have people solved this? publish each image in order first so the 'real' target gets pulled? ( i was hoping to package the images before publishing).