Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AMI cached docker images are not present on instances with EnableDockerUserNamespaceRemap: true #950

Open
keithduncan opened this issue Oct 19, 2021 · 2 comments
Labels
bug docker Relates to the use of Docker on stack agents

Comments

@keithduncan
Copy link
Contributor

Ideally we can find a way to produce an AMI which when built upon to cache resources supports both EnableDockerUserNamespaceRemap: true and EnableDockerUserNamespaceRemap: false.

Presently the best workaround to support pre-cached images is to set EnableDockerUserNamespaceRemap: false in you stack’s parameters.

@woodhull
Copy link

Are there docs for AMI cached docker images?

We'd be interested in this (we're already running a fork of the stack) to improve build performance re: downloading the docker images for some slow moving service dependencies that we use via docker-compose.

@keithduncan
Copy link
Contributor Author

There aren’t docs at this time. We’ve had success using buildkite/image-builder or packer to build on top of our base images and run docker pull. The resulting image can then be passed to a stack using the ImageId or ImageIdParameter template parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug docker Relates to the use of Docker on stack agents
Projects
None yet
2 participants