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
This issue was originally opened by @boblechat in hashicorp/packer#11180 and has been migrated to this repository. The original issue description is below.
I have a use case where I pull a base image from a private registry where I need to log into.
Then in my build process, I tag and push the newly created image in the same private registry.
When I read the log produced, I see that packer log out automatically after pulling the image which is a bit annoying because I have to log in again in the docker-tag post-processor.
Is there a way to stay connected once authenticated?
The text was updated successfully, but these errors were encountered:
Currently, each plugin implements/call for its own login/creation independently of other plugins. There is a 'centralized' plugin credential feature we would like to build, but it's not for right now 🙂.
azr
changed the title
Docker builder: is it possible to stay logged-in once authenticated on a private registry?
Docker builder: is it possible to stay logged-in once authenticated on a private registry? [ plugin credentials ]
Aug 18, 2021
This issue was originally opened by @boblechat in hashicorp/packer#11180 and has been migrated to this repository. The original issue description is below.
I have a use case where I pull a base image from a private registry where I need to log into.
Then in my build process, I tag and push the newly created image in the same private registry.
When I read the log produced, I see that packer log out automatically after pulling the image which is a bit annoying because I have to log in again in the docker-tag post-processor.
Is there a way to stay connected once authenticated?
The text was updated successfully, but these errors were encountered: