This question mixes Ansible and Packer as I am having a lot of problems locating the issue. We have a build server that currently executes an Ansible playbook that calls packer to create new images. Works Great. I am testing doing this from inside a docker container using Code Build and bitbucket pipelines.
The first weirdness we encountered was Packer not being able to determine what user the container was running as and we solved that by setting the environment variable USER=root. After that packer is able to connect to AWS and spin up an instance to run the additional playbooks. There seems to be a difference in the way packer is executing Ansible from the old build server and the new container builder. The same scripts fail in the containerized build. It seems it is not running commands as sudo and they fail because of permissions. Any insight is helpful. Thanks -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/a1136a06-6e8f-4057-ba16-3956f696d1c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
