Unable to run containers via podman compose

[chuck-flowers]

Describe the bug
I'm getting what appears to be a network error whenever I try to start a container using podman compose up serviceName.

This doesn't appear to be a bug in podman because I'm able to podman run -it --rm imageName without seeing the issue.

To Reproduce
Steps to reproduce the behavior:

1. Author the following compose.yml file:

services:
  busybox:
    image: docker.io/busybox:1

2. Run the following command:

podman compose up busybox

Expected behavior
I would be prompted with busybox's shell
Actual behavior
I see the following output and am returned to my host's shell

>>>> Executing external compose provider "/home/cflowers/.local/bin/podman-compose". Please see podman-compose(1) for how to disable this message. <<<<

uspack-app-tracking_busybox_1
uspack-app-tracking_busybox_1
61ebc176e0c1f00b824430e81cea528d255e354dd386254ad4bb99ecb250da38
[busybox]               | internal:0:0-0: Error: Could not process rule: No such file or directory
[busybox]               |
[busybox]               | internal:0:0-0: Error: Could not process rule: No such file or directory
[busybox]               |
[busybox]               | Error: unable to start container 61ebc176e0c1f00b824430e81cea528d255e354dd386254ad4bb99ecb250da38: netavark: nftables error: nft did not return successfully while applying ruleset

Output

$ podman-compose version
podman-compose version 1.2.0
podman version 5.3.1

$ podman --version 
podman version 5.3.1

$ podman-compose up
f971f4f508a9ab51f88b24d827bfb834cc7399072e2b28659ab31e26cde56cef
3fc220f7a9c6e653457f60e2a73b458334b275eb1427da20792ff7cad0717d25
[busybox] | internal:0:0-0: Error: Could not process rule: No such file or directory
[busybox] |
[busybox] | internal:0:0-0: Error: Could not process rule: No such file or directory
[busybox] |
[busybox] | Error: unable to start container 3fc220f7a9c6e653457f60e2a73b458334b275eb1427da20792ff7cad0717d25: netavark: nftables error: nft did not return successfully while applying ruleset

Environment:

• OS: WSL2 openSUSE Tumbleweed
• podman version: 5.3.1
• podman compose version: d9fc8e9

Additional context

I was able to reproduce this issue with the version of podman-compose in the openSUSE Tumbleweed repositories as well as installing using the docker build described in the podman-compose repository's README.

[chuck-flowers]

I should also add, that configuring the service in the compose.yml file to use network_mode: host, the issue goes away. I hope that helps narrow down what's going on.