Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🖐️ Best practices for local registries or passing containers from one module to another in the CLI #7165

Open
nrs-status opened this issue Apr 23, 2024 · 0 comments

Comments

@nrs-status
Copy link

nrs-status commented Apr 23, 2024

I'd like to pass a container from one module to another. I'm currently doing something like this:

TTL_SH_CONTAINER=$(dagger -m github.com/Dudesons/daggerverse/infrabox call terragrunt container \
...
publish --address ttl.sh/terragrunt-$RANDOM)

dagger -m github.com/Dudesons/daggerverse call terragrunt \          
with-container --ctr $TTL_SH_CONTAINER \
...

This definitely works at the moment, but I wish I could keep it local without needing to go through ttl.sh. What would be considered the best practices for such a workflow? I attempted to set up a local docker registry instead, but the issue is that it requires tagging the image first before pushing it to the local registry and I haven't seen any facility to do so in dagger. Any inputs or tips are highly appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant