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 Mar 15, 2022. It is now read-only.
Dear hashicorp team
Is there a way to autoexpose the packerport onto the Dockerhost for Provisioning the user-data / meta-data file via http out of the docker network?
Would be awesome, because currently I'm using the packer:light image as a gitlab runner and so the packer http server only exposes itself in the docker network for prov the user-data / meta-data stuff.
Would be nice if you implement this or show me a valid workaround.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dear hashicorp team
Is there a way to autoexpose the packerport onto the Dockerhost for Provisioning the user-data / meta-data file via http out of the docker network?
Would be awesome, because currently I'm using the packer:light image as a gitlab runner and so the packer http server only exposes itself in the docker network for prov the user-data / meta-data stuff.
Would be nice if you implement this or show me a valid workaround.
The text was updated successfully, but these errors were encountered: