Ability to select Network Type

[PHHENS]

Describe your feature request

Dear Developper,
Thanks for creating pods which is a pretty nice tool.
It would be great to be able to select existing network at container creation (bridge based network, macvlan based network ...).

Thanks for understanding this advanced need.

[PHHENS]

Dear Developer,
I've seen there is an Network Panel branch active, what is the status ?
Do you plan a release including this Network Panel ?
Thanks for your answer.

[marhkb]

Dear Developer, I've seen there is an Network Panel branch active, what is the status ? Do you plan a release including this Network Panel ? Thanks for your answer.

I would like to merge it. The problem is that podman does not raise an event when you create a network (in contrast to containers, images, pods, etc). So I can't detect new Networks as they are created. See https://docs.podman.io/en/latest/markdown/podman-events.1.html

Docker on the other hand does it right (https://docs.docker.com/reference/cli/docker/system/events/#networks). So I think this is a design flaw in podman.

Currently, I have not much time to report the issue to the podman developers.
So, any help in getting this issue resolved is appreciated.

[PHHENS]

Dear Marcus, Thanks for your feedback :

…

-------------------------------------------------------------------------------------------------------------- Issue verified here : Whith docker : docker network create -d macvlan -o parent=eth0 netph2 docker remove network netph2 docker events 2024-09-22T11:13:53.675328084+02:00 network create e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 (name=netph2, type=macvlan) 2024-09-22T11:15:02.855986547+02:00 network destroy e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 (name=netph2, type=macvlan)

-------------------------------------------------------------------------------------- With podman : podman network create -d macvlan -o parent=eth0 netph2 podman remove network netph2 podman events NOTHING HERE

------------------------------------------------------------------------------------------- Will try to create ticket later ... Thanks Le sam. 21 sept. 2024 à 11:59:53 -07:00:00, Marcus Behrendt ***@***.***> a écrit :

> Dear Developer, I've seen there is an Network Panel branch active, > what is the status ? Do you plan a release including this Network > Panel ? Thanks for your answer. > I would like to merge it. The problem is that podman /does not/ raise an event when you create a network (in contrast to containers, images, pods, etc). So I can't detect new Networks as they are created. Docker on the other hand does it right (<https://docs.docker.com/reference/cli/docker/system/events/#networks>). So I think this is a design flaw in podman. Currently, I have not much time to report the issue to the podman developers. So, any help in getting this issue resolved is appreciated. — Reply to this email directly, view it on GitHub <#785 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI2HQZAXD74HGTP34UQJY7DZXW62TAVCNFSM6AAAAABOPRC4A6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGI4DQNRYHE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[PHHENS]

Dear Marcus, Issue declared on podman github : <containers/podman#24032> Thanks Le dim. 22 sept. 2024 à 11:19:51 +02:00:00, ph ***@***.***> a écrit :

…

Dear Marcus, Thanks for your feedback : -------------------------------------------------------------------------------------------------------------- Issue verified here : Whith docker : docker network create -d macvlan -o parent=eth0 netph2 docker remove network netph2 docker events 2024-09-22T11:13:53.675328084+02:00 network create e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 (name=netph2, type=macvlan) 2024-09-22T11:15:02.855986547+02:00 network destroy e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 (name=netph2, type=macvlan) -------------------------------------------------------------------------------------- With podman : podman network create -d macvlan -o parent=eth0 netph2 podman remove network netph2 podman events NOTHING HERE ------------------------------------------------------------------------------------------- Will try to create ticket later ... Thanks Le sam. 21 sept. 2024 à 11:59:53 -07:00:00, Marcus Behrendt ***@***.***> a écrit : >> Dear Developer, I've seen there is an Network Panel branch active, >> what is the status ? Do you plan a release including this Network >> Panel ? Thanks for your answer. >> > I would like to merge it. The problem is that podman /does not/ > raise an event when you create a network (in contrast to containers, > images, pods, etc). So I can't detect new Networks as they are > created. > > Docker on the other hand does it right > (<https://docs.docker.com/reference/cli/docker/system/events/#networks>). > So I think this is a design flaw in podman. > > Currently, I have not much time to report the issue to the podman > developers. > So, any help in getting this issue resolved is appreciated. > > — > Reply to this email directly, view it on GitHub > <#785 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AI2HQZAXD74HGTP34UQJY7DZXW62TAVCNFSM6AAAAABOPRC4A6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGI4DQNRYHE>. > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[PHHENS]

Dear Marcus, Answer from podman git (paul holzinger): We do have events for network connect/disconnect. The fact that we do have have them for create/disconnect seems like an oversight. Thanks Le dim. 22 sept. 2024 à 11:43:04 +02:00:00, ph ***@***.***> a écrit :

…

Dear Marcus, Issue declared on podman github : <containers/podman#24032> Thanks Le dim. 22 sept. 2024 à 11:19:51 +02:00:00, ph ***@***.***> a écrit : > Dear Marcus, > > Thanks for your feedback : > > -------------------------------------------------------------------------------------------------------------- > Issue verified here : > > Whith docker : > docker network create -d macvlan -o parent=eth0 netph2 > docker remove network netph2 > > docker events > > 2024-09-22T11:13:53.675328084+02:00 network create > e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 > (name=netph2, type=macvlan) > 2024-09-22T11:15:02.855986547+02:00 network destroy > e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 > (name=netph2, type=macvlan) > > -------------------------------------------------------------------------------------- > > With podman : > podman network create -d macvlan -o parent=eth0 netph2 > podman remove network netph2 > > podman events > NOTHING HERE > > ------------------------------------------------------------------------------------------- > > Will try to create ticket later ... > > Thanks > > Le sam. 21 sept. 2024 à 11:59:53 -07:00:00, Marcus Behrendt > ***@***.***> a écrit : >>> Dear Developer, I've seen there is an Network Panel branch active, >>> what is the status ? Do you plan a release including this Network >>> Panel ? Thanks for your answer. >>> >> I would like to merge it. The problem is that podman /does not/ >> raise an event when you create a network (in contrast to >> containers, images, pods, etc). So I can't detect new Networks as >> they are created. >> >> Docker on the other hand does it right >> (<https://docs.docker.com/reference/cli/docker/system/events/#networks>). >> So I think this is a design flaw in podman. >> >> Currently, I have not much time to report the issue to the podman >> developers. >> So, any help in getting this issue resolved is appreciated. >> >> — >> Reply to this email directly, view it on GitHub >> <#785 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AI2HQZAXD74HGTP34UQJY7DZXW62TAVCNFSM6AAAAABOPRC4A6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGI4DQNRYHE>. >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >>

[PHHENS]

Dear Marcus, Seems to be, now, resolved in podman : <containers/podman@c23d9c6> Thanks Le mar. 24 sept. 2024 à 09:53:09 +02:00:00, ph ***@***.***> a écrit :

…

Dear Marcus, Answer from podman git (paul holzinger): We do have events for network connect/disconnect. The fact that we do have have them for create/disconnect seems like an oversight. Thanks Le dim. 22 sept. 2024 à 11:43:04 +02:00:00, ph ***@***.***> a écrit : > Dear Marcus, > > Issue declared on podman github : > <containers/podman#24032> > > Thanks > > > Le dim. 22 sept. 2024 à 11:19:51 +02:00:00, ph ***@***.***> a > écrit : >> Dear Marcus, >> >> Thanks for your feedback : >> >> -------------------------------------------------------------------------------------------------------------- >> Issue verified here : >> >> Whith docker : >> docker network create -d macvlan -o parent=eth0 netph2 >> docker remove network netph2 >> >> docker events >> >> 2024-09-22T11:13:53.675328084+02:00 network create >> e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 >> (name=netph2, type=macvlan) >> 2024-09-22T11:15:02.855986547+02:00 network destroy >> e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 >> (name=netph2, type=macvlan) >> >> -------------------------------------------------------------------------------------- >> >> With podman : >> podman network create -d macvlan -o parent=eth0 netph2 >> podman remove network netph2 >> >> podman events >> NOTHING HERE >> >> ------------------------------------------------------------------------------------------- >> >> Will try to create ticket later ... >> >> Thanks >> >> Le sam. 21 sept. 2024 à 11:59:53 -07:00:00, Marcus Behrendt >> ***@***.***> a écrit : >>>> Dear Developer, I've seen there is an Network Panel branch >>>> active, what is the status ? Do you plan a release including this >>>> Network Panel ? Thanks for your answer. >>>> >>> I would like to merge it. The problem is that podman /does not/ >>> raise an event when you create a network (in contrast to >>> containers, images, pods, etc). So I can't detect new Networks as >>> they are created. >>> >>> Docker on the other hand does it right >>> (<https://docs.docker.com/reference/cli/docker/system/events/#networks>). >>> So I think this is a design flaw in podman. >>> >>> Currently, I have not much time to report the issue to the podman >>> developers. >>> So, any help in getting this issue resolved is appreciated. >>> >>> — >>> Reply to this email directly, view it on GitHub >>> <#785 (comment)>, >>> or unsubscribe >>> <https://github.com/notifications/unsubscribe-auth/AI2HQZAXD74HGTP34UQJY7DZXW62TAVCNFSM6AAAAABOPRC4A6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGI4DQNRYHE>. >>> You are receiving this because you authored the thread.Message ID: >>> ***@***.***> >>>