Description of problem: `podman-compose run` fails when running a single service. Version-Release number of selected component (if applicable): podman-compose-0.1.8-1.fc34.noarch How reproducible: Everytime Steps to Reproduce: 1. podman-compose run postgres (with valid Dockerfile and docker-compose) 2. 3. Actual results: $ podman-compose run postgres ['podman', '--version', ''] using podman version: 3.4.2 podman pod create --name=go-automate-it --share net --infra-name=go-automate-it_infra -p 5432:5432 -p 2112:2112 -p 8080:8080 Error: error adding pod to state: name "go-automate-it" is in use: pod already exists exit code: 125 ** excluding: set() Traceback (most recent call last): File "/usr/bin/podman-compose", line 33, in <module> sys.exit(load_entry_point('podman-compose==0.1.8', 'console_scripts', 'podman-compose')()) File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1762, in main podman_compose.run() File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1036, in run cmd(self, args) File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1268, in wrapped return func(*args, **kw) File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1513, in compose_run compose.commands['up'](compose, up_args) File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1268, in wrapped return func(*args, **kw) File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1421, in compose_up compose.commands['build'](compose, build_args) File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1268, in wrapped return func(*args, **kw) File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1375, in compose_build build_one(compose, args, cnt) File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1353, in build_one if args.no_cache: AttributeError: 'Namespace' object has no attribute 'no_cache' Expected results: Running the service succeeds. Additional info: Upstream fix: https://github.com/containers/podman-compose/commit/749d188321c4662e98de84b8c1449d10b8b2d647
FEDORA-2021-378dabccc4 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-378dabccc4
FEDORA-2021-7a2ee2e25e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7a2ee2e25e
FEDORA-2021-7a2ee2e25e has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-7a2ee2e25e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7a2ee2e25e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-378dabccc4 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-378dabccc4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-378dabccc4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-378dabccc4 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-7a2ee2e25e has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.