Closed joshi-mohit closed 4 months ago
Possibly becasue of python3 pointing to python3.6 --> will recheck and reopen if needed
Hi, got the same error here on RHEL8X Is python 3.6 not supported anymore ? We got VMs running Python 3.6.8 and Podman Compose 1.0.6 without any problems. I tried to follow the same installation that we did on our older VMs and we got this error.
# podman-compose version
Traceback (most recent call last):
File "/usr/local/bin/podman-compose", line 8, in <module>
sys.exit(main())
File "/usr/local/lib/python3.6/site-packages/podman_compose.py", line 3504, in main
asyncio.run(async_main())
AttributeError: module 'asyncio' has no attribute 'run'
Describe the bug I get the error on running a compose file
Traceback (most recent call last): File "/usr/local/bin/podman-compose", line 11, in
load_entry_point('podman-compose==1.0.7', 'console_scripts', 'podman-compose')()
File "/usr/local/lib/python3.6/site-packages/podman_compose.py", line 3246, in main
asyncio.run(async_main())
AttributeError: module 'asyncio' has no attribute 'run'
version: '3.3' services: zookeeper: image: 'docker.io/bitnami/zookeeper:3-debian-10' expose:
[azureuser@MJ-RedHat-SaaS-PodMan pre-requisites]$ podman --version podman version 4.2.0
[azureuser@MJ-RedHat-SaaS-PodMan pre-requisites]$ python3 --version Python 3.6.8
installed podman-compose sudo pip3 install https://github.com/containers/podman-compose/archive/devel.tar.gz
To Reproduce
even running podman-compose --version is returing same error
Expected behavior supposed to run
Actual behavior What is the behavior you actually got and that should not happen.
Output
Environment:
Additional context
Add any other context about the problem here.