-
Notifications
You must be signed in to change notification settings - Fork 61
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
Add netavark and aardvark-dns #84
Comments
Sure, given that these binaries are already shipped with the official fedora-based podman image, go for it! Though, I wonder in which scenario(s) they are used with podman. So, when you create a pull request, it would be great if you'd add a corresponding e2e test(s) (just a simple podman CLI call within one of the *.bats files here) to illustrate how they are used and to ensure they remain usable during subsequent updates. |
Having these DNS features in podman-static would be very usefull indeed ! At present time basic "podman compose" stacks don't work properly with static podman build (each container can't see/resolve the other ones although they should be in same virtual network created by compose). Getting this to work would be great :-) Thanks you all for your hard work ! Can't wait to see these compose features working in static version |
It took a while but now this was addressed within #91: Finally the v5.1.1 release is shipped with netavark and pasta (instead of CNI and slirp4netns) as well as aardvark-dns. |
It works great with podamn compose ! Thanks a lot, this is very helpfull |
Would you be open to a PR to add netavark and aardvark-dns?
The text was updated successfully, but these errors were encountered: