You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
Ideally we can find a way to produce an AMI which when built upon to cache resources supports both
EnableDockerUserNamespaceRemap: true
andEnableDockerUserNamespaceRemap: false
.Presently the best workaround to support pre-cached images is to set
EnableDockerUserNamespaceRemap: false
in you stack’s parameters.The text was updated successfully, but these errors were encountered: