Packer实例访问AWS中的私有Docker注册表

Question

With Jenkins, running in my build VPC, I've got a job that runs a Packer build to bake an AMI. During the AMI creation, I have to pull from my private Docker registry, also running in my build VPC.

I've got my registry locked right down, so it's only accessible from Jenkins or from my office.

When baking the AMI, I need to pull a docker image and start a container from it. However, because Packer's instance isn't permitted to access the registry, this fails.

I can't figure out how to dynamically allow access to the registry for this instance.

Is there a way to do this with Packer (or Jenkins), without having to have the registry wide open all the time?

Answer 1

I would have Packer launch the instance being build into a security group using the settings: security_group_id or security_groups_ids . If you add that group to the security for the Docker Registry instance then communication should be allowed at the networking level. Permissions are all on you.

https://packer.io/docs/builders/amazon-ebs.html