We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[email protected]
In our docker-compose we use links https://docs.docker.com/compose/networking/#link-containers when trying to start awx docker compose development environment using podman this is not supported
links
we should be able to remove use of links
awx: 24.1.1.dev27+g71358e5cb5
docker development environment
no
No response
MacOS
install podman desktop on mac and try to use make docker-compose to start docker compose development environment
make docker-compose
docker-compose development environment starts
Error response from daemon: bad parameter: link is not supporte
podman version 5.1.0-dev applehv virtualization
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Please confirm the following
[email protected]
instead.)Bug Summary
In our docker-compose we use
links
https://docs.docker.com/compose/networking/#link-containerswhen trying to start awx docker compose development environment using podman this is not supported
we should be able to remove use of links
AWX version
awx: 24.1.1.dev27+g71358e5cb5
Select the relevant components
Installation method
docker development environment
Modifications
no
Ansible version
No response
Operating system
MacOS
Web browser
No response
Steps to reproduce
install podman desktop on mac and try to use
make docker-compose
to start docker compose development environmentExpected results
docker-compose development environment starts
Actual results
Error response from daemon: bad parameter: link is not supporte
Additional information
podman version 5.1.0-dev
applehv virtualization
The text was updated successfully, but these errors were encountered: