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

Allow CLI to use existing podman machine instead of making a new one #1801

Open
2 tasks
techgnosis opened this issue Feb 5, 2025 · 0 comments
Open
2 tasks

Comments

@techgnosis
Copy link

  • [ y] I have checked that a similar feature request does not already exist.

✍️ Is your feature request related to a problem? Please describe.
astro dev start creates its own podman machine instead of allowing you to use an existing one. Sometimes you need to use an existing podman machine based on how it is configured, like user mode networking for example.

🧩 Describe the solution you'd like
Add a CLI flag, such as astro dev start --podman-machine my-existing-machine. Then the astro CLI can find the appropriate socket or pipe and use it, instead of having the using need to set DOCKER_HOST.

🤔 Describe alternatives you've considered
The alternative already exists, which is to set DOCKER_HOST to the location of the podman machine socket or pipe. That requires some knowledge of how to find the socket or pipe and knowledge of how to set an environment variable.

Is your feature request specific to a particular Astronomer Platform?

  • Astro
  • Software
  • [y ] None/Unknown

💡 Additional context

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