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
{{ message }}
This repository has been archived by the owner on Aug 22, 2024. It is now read-only.
The AMI build process works by downloading and saving the Conjur image locally before uploading the gzipped tar file to the AMI. This is super inefficient.
A better approach would be to download the Conjur image directly to the EC2 instance before saving it off as an AMI. Our registry credentials would need to be injected onto the instance prior to docker pull ...., then removed from the instance after the image has been pulled.
The text was updated successfully, but these errors were encountered:
FWIW, I've been experimenting with using DockerInDocker to log in and pull an image without landing the credentials on the host.
I'm currently doing the docker pull, docker save, scp dance to the get image to the remote instance, but this is inspiring me to see I can pull it directly.
The AMI build process works by downloading and saving the Conjur image locally before uploading the gzipped tar file to the AMI. This is super inefficient.
A better approach would be to download the Conjur image directly to the EC2 instance before saving it off as an AMI. Our registry credentials would need to be injected onto the instance prior to
docker pull ....
, then removed from the instance after the image has been pulled.The text was updated successfully, but these errors were encountered: