Fix podman test compatibility: remove hardcoded network backend by Copilot · Pull Request #14422 · ComplianceAsCode/content

Copilot AI changed the title [WIP] Debug Podman with slirp4netns Remove unsupported mtu parameter from podman slirp4netns configuration

Feb 18, 2026

Copilot AI changed the title Remove unsupported mtu parameter from podman slirp4netns configuration Fix podman container tests on openSUSE and systems with varying network backends

Feb 18, 2026

Copilot AI changed the title Fix podman container tests on openSUSE and systems with varying network backends Fix podman test compatibility: remove hardcoded network backend

Feb 19, 2026

alanmcanonical

teacup-on-rockingchair

Mab879

@teacup-on-rockingchair

Co-authored-by: teacup-on-rockingchair <315160+teacup-on-rockingchair@users.noreply.github.com>
- Remove --network slirp4netns to use podman's default network backend
- Add better error handling in extract_port_map for edge cases
- Preserve original exception for better debugging in get_ssh_port
- Fixes compatibility across different podman/slirp4netns versions

Co-authored-by: teacup-on-rockingchair <315160+teacup-on-rockingchair@users.noreply.github.com>
- Remove redundant logging statement (exception is preserved via raise...from)
- Simplify validation logic by removing redundant length check
- Keep exception chaining for better debugging

Co-authored-by: teacup-on-rockingchair <315160+teacup-on-rockingchair@users.noreply.github.com>

@Mab879 @teacup-on-rockingchair