Has anyone run into multi-stage builds across pants targets not properly invalidating the base image? We're trying to upgrade the python version installed in our base container, but building the child images doesn't cause the base image to get rebuilt. We depend on the base image like so:

ARG BASE_IMAGE=docker/prod:prod
FROM $BASE_IMAGE

Which Pants version? I vaguely recall an issue being fixed a while ago.

2.24.0

OK, so not that

for the child targets do you have

pull=True

? and are you using docker or podman?

no and docker

if you... do pull=True does it pull the new base image?

Adding pull=True seems to not work

manifest for ...<http://dkr.ecr.us-east-1.amazonaws.com/prod:0.1-ba4806ac8d09d8612e7fb5b250d38e2fc15e275e65982471aea0fe38c9e1794a|dkr.ecr.us-east-1.amazonaws.com/prod:0.1-ba4806ac8d09d8612e7fb5b250d38e2fc15e275e65982471aea0fe38c9e1794a> not found: manifest unknown: Requested image not found

docs seem to indicate this is a known limitation https://www.pantsbuild.org/dev/reference/targets/docker_image#pull

NOTE: This option cannot be used on images that build off of "transitive" base images referenced by address (i.e. FROM path/to/your/base/Dockerfile).