riisi

@ndellosa95 I've looked into the issue with multiple dependent images and was able to get it working using the [Containerd Image Store](https://docs.docker.com/desktop/containerd/). Here's what I've used to test this locally...

Closing this as I believe it's fixed since 2.19 with above approach - let me know otherwise.

FWIW I don't have any concerns with this implementation - I think it's a great feature to have. Looks like GCP (which i'm working with now) has support for pull-through...

I've reworked the package integration test to cover the case of importing another workspace package, which triggered the integrity file conflict. In doing so, I found a bug, which held...

Came across this today. There's some discussion on Slack about trying to get keyring authentication working, but seems no success. I was able to get it working with the oauth...

@mark-thm Have you tried the following? 1. Enable BuildKit if necessary (it is the default in later versions of Docker): ``` ❯ export DOCKER_BUILDKIT=1 ``` 2. Allow Pants to read...

Try this (e.g.) also and I think that should get you going for now: Create a builder using a [build driver](https://docs.docker.com/build/drivers/) that is compatible with the cache backend: ``` ❯...

Which CI system are you using? I was just looking into the same for Github Actions recently and it looks straightforward, but not sure about others.

@rajeshwar-nu Yes, this is coming in 2.19 as part of https://github.com/pantsbuild/pants/pull/20154 as mentiond above

If you are deploying the lambda from a container image (https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/), then the AWS calculated hash will be the image digest. Making a change to the image source, building and...