Skip to content

Show networks top level element in command config - #1522

Open
mokibit wants to merge 1 commit into
containers:mainfrom
mokibit:config-add-network
Open

Show networks top level element in command config#1522
mokibit wants to merge 1 commit into
containers:mainfrom
mokibit:config-add-network

Conversation

@mokibit

@mokibit mokibit commented Jul 27, 2026

Copy link
Copy Markdown
Collaborator

Previously podman-compose config omitted the networks section and did not reflect runtime network resolution such as default network injection. Now it outputs the effective network configuration, including created and external networks with correct names, matching actual compose behavior.

Fixes #623.

@mokibit
mokibit force-pushed the config-add-network branch 3 times, most recently from 76ab083 to 822673d Compare July 28, 2026 13:08
Previously `podman-compose config` omitted the `networks` section and
did not reflect runtime network resolution such as default network
injection. Now it outputs the effective network configuration, including
created and external networks with correct names, matching actual
compose behavior.

Signed-off-by: Monika Kairaityte <monika@kibit.lt>
@mokibit
mokibit force-pushed the config-add-network branch from 822673d to 504d6f5 Compare July 28, 2026 14:05
Comment thread podman_compose.py


def build_compose_config(compose: PodmanCompose) -> dict[str, Any]:
config: dict[str, Any] = {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This approach will lose all custom keys that it does not know about.

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

Successfully merging this pull request may close these issues.

podman-compose config should append network name

2 participants