-
Notifications
You must be signed in to change notification settings - Fork 457
New issue
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
Podman-compose is not handling networks: RuntimeError: missing networks: #463
Comments
Question?what version of podman-compose are you using? NOTEthe here is an example how to specify static ip version: "3"
networks:
app1_container_network:
ipam:
driver: default
config:
- subnet: "172.20.0.0/16"
services:
app1:
image: busybox
command: httpd -f -p 8080 -h /etc/
networks:
app1_container_network:
ipv4_address: 172.20.0.11 NOTE 2specifying address is against the 12 factor you should use port mapping not ip address mapping. |
I am running:
just to confirm. this will still put it in the pre-existing network "podman" correct? Either way when I set my compose file as such:
it still spits this error:
|
would you please try latest branch.
I've tested it with equivalent yaml and it worked ---
version: "3"
networks:
podman:
ipam:
driver: default
config:
- subnet: "10.88.2.0/24"
services:
web1:
image: busybox
command: httpd -f -p 8080 -h /etc/
networks:
podman:
ipv4_address: 10.88.2.10
web2:
image: busybox
command: httpd -f -p 8080 -h /etc/
networks:
podman:
ipv4_address: 10.88.2.11 |
updating to the newest version fixed it. just for reference when wanting to use a pre-existing network you can ley it out as such:
I also notice it puts my containers in a pod now, which I like, but is there a command to stop that from happening in the compose file. or just a general way of setting pod configuration? |
to prevent creating a pod
to adjust pod params
there is no way to control that from inside the yaml |
Just a note that upgrading to podman-compose 1.0.4 fixed the same problem for me |
results in Do you have an example? |
Any plan to do a new release? |
@muayyad-alsadi is there any plan on the podman-compose 1.0.4 rpm release? Fedora 37 is still using the 1.0.3. |
I'm facing the same issue with newer versions: podman-compose --version
podman-compose version: 1.0.6
['podman', '--version', '']
using podman version: 3.4.4
podman-compose version 1.0.6
podman --version
podman version 3.4.4
exit code: 0 podman-compose up
Error tearing down partially created network namespace for container c43...c48: CNI network "my_bridge" not found The network itself was created and exists: podman network ls
WARN[0000] Error validating CNI config file /etc/cni/net.d/my_bridge.conflist: [plugin bridge does not support config version "1.0.0" plugin portmap does not support config version "1.0.0" plugin firewall does not support config version "1.0.0" plugin tuning does not support config version "1.0.0"]
NETWORK ID NAME VERSION PLUGINS
2f259bab93aa podman 0.4.0 bridge,portmap,firewall,tuning
177b12cc34e2 my_bridge 1.0.0 bridge,portmap,firewall,tuning,dnsname Edit: It only works when I use the preconfigured bridge network networks:
my_bridge:
external:
name: podman |
Having the exact same issue as @mreiche here. Any ideas?? |
I use |
I came back to this, because my problem seems to be related to Podman 3.4.4 on Ubuntu 22.04 and there is no official newer version available and I need to get this fixed. So this is my workaround. When I created an external network, I saw a list with different versions. podman network ls
NETWORK ID NAME VERSION PLUGINS
2f259bab93aa podman 0.4.0 bridge,portmap,firewall,tuning
8ac92e008a0e my_network 1.0.0 bridge,portmap,firewall,tuning,dnsname and a suspicious message:
So I edited podman network ls
NETWORK ID NAME VERSION PLUGINS
2f259bab93aa podman 0.4.0 bridge,portmap,firewall,tuning
8ac92e008a0e my_network 0.4.0 bridge,portmap,firewall,tuning,dnsname This network I could use with networks:
default:
name: my_network
external: true where also DNS resolution works now. |
Is that a fix or a way to mute version compatibility warnings?
sob., 27 sty 2024, 20:09 użytkownik Mike Reiche ***@***.***>
napisał:
… I came back to this, because my problem seems to be related to Podman
3.4.4 on Ubuntu 22.04, because there is no official newer version available
and I need to get this fixed. So this is my workarround.
When I created an external network, I saw a list with different versions.
podman network ls
NETWORK ID NAME VERSION PLUGINS
2f259bab93aa podman 0.4.0 bridge,portmap,firewall,tuning
8ac92e008a0e my_network 1.0.0 bridge,portmap,firewall,tuning,dnsname
and a suspicious message:
´´´
WARN[0000] Error validating CNI config file
/etc/cni/net.d/my_network.conflist: [plugin bridge does not support config
version "1.0.0" plugin portmap does not support config version "1.0.0"
plugin firewall does not support config version "1.0.0" plugin tuning does
not support config version "1.0.0"]
So I edited `/etc/cni/net.d/my_network.conflist` and changed the version to `0.4.0`.
```shell
podman network ls
NETWORK ID NAME VERSION PLUGINS
2f259bab93aa podman 0.4.0 bridge,portmap,firewall,tuning
8ac92e008a0e my_network 0.4.0 bridge,portmap,firewall,tuning,dnsname
This network I could use with podman-compose like:
networks:
default:
name: my_network
external: true´´´where also DNS resolution works now.
—
Reply to this email directly, view it on GitHub
<#463 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4DH6ZWOEM6G2H7LKZT37LYQVGGFAVCNFSM5R4QSO3KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJRGMZDSOBVGMZQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
It's a workaround. |
I have the same issue on:
Weirdly, I only have this issue on the user account I specifically created for podman. On my user account on the same system, the same compose file just works. I nuked Table of Differences
I tested that with this simple compose file: version: "2"
services:
test:
image: hello-world |
When trying to make a static IP setting based specifically on this documentation under the "ipv4_address, ipv6_address" section:
https://docs.docker.com/compose/compose-file/compose-file-v3/
I am receiving the "RuntimeError: missing networks: default,podman" error. I have tried a variety of other methods to no avail. it seems that podman-compose is not properly reading the networks: section in the yaml
here is my compose file:
And here are the results I get:
I have tried using default as well as "network_mode" neither gave good results.
please let me know if there is any other info needed or things you would like me to try.
The text was updated successfully, but these errors were encountered: