fix: init with podman and netns=host create containers without ports - #1694
Open
m3nax wants to merge 1 commit into
Open
fix: init with podman and netns=host create containers without ports#1694m3nax wants to merge 1 commit into
m3nax wants to merge 1 commit into
Conversation
Signed-off-by: Manuel Menegazzo <manuel.menegazzo@outlook.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fix
dapr initcreating containers in podman without published portsOn my development workstation (Windows, with podman and a WSL podman machine), running
dapr init --dev --container-runtime=podmanwith Dapr CLI 1.18 created all the Daprcontainers (
dapr_placement,dapr_scheduler,dapr_redis,dapr_zipkin) with nopublished ports.
podman psshowed an empty PORTS column and nothing was reachable fromthe host, which made the local Dapr setup unusable.
The root cause is the podman
netnsdefault incontainers.conf. When the CLI does not passan explicit
--network, podman applies that default. If it is set tohost, every-pmapping is silently discarded.
Issue reference
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: