-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Events for Network #24032
Labels
Good First Issue
This issue would be a good issue for a first time contributor to undertake.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
We do have events for network connect/disconnect. The fact that we do have have them for create/remove seems like an oversight. |
we have always been hesitant to do this due to "event fatigue". But agree with @Luap99 , it makes sense for certain. |
It makes sense for a container management GUI (gnome pods) with a
network management panel :
(<https://github.com/marhkb/pods/tree/feat/networks/panel>)...
Le mer. 25 sept. 2024 à 06:55:57 -07:00:00, Brent Baude
***@***.***> a écrit :
… we have always been hesitant to do this due to "event fatigue". But
agree with @Luap99 <https://github.com/Luap99> , it makes sense for
certain.
—
Reply to this email directly, view it on GitHub
<#24032 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI2HQZFOYI4QZA3SRA24N3TZYK6G3AVCNFSM6AAAAABOUMZOUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGE3DKMJXHE>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I would like to work on this issue 👀 . |
Thanks @Sativarsainath-26 It is all yours. |
A friendly reminder that this issue had no activity for 30 days. |
Sativarsainath-26
added a commit
to Sativarsainath-26/podman
that referenced
this issue
Oct 31, 2024
…dman events Signed-off-by: Sainath Sativar <Sativar.sainath@gmail.com>
Sativarsainath-26
added a commit
to Sativarsainath-26/podman
that referenced
this issue
Oct 31, 2024
…dman events Signed-off-by: Sainath Sativar <Sativar.sainath@gmail.com>
Sativarsainath-26
added a commit
to Sativarsainath-26/podman
that referenced
this issue
Oct 31, 2024
…dman events Signed-off-by: Sainath Sativar <Sativar.sainath@gmail.com>
Sativarsainath-26
added a commit
to Sativarsainath-26/podman
that referenced
this issue
Nov 1, 2024
This commit resolves an issue where network creation and removal events were not being logged in `podman events`. A new function has been introduced in the `events` package to ensure consistent logging of network lifecycle events. This update will allow users to track network operations more effectively through the event log, improving visibility and aiding in debugging network-related issues. Fixes: containers#24032 Signed-off-by: Sainath Sativar <Sativar.sainath@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Good First Issue
This issue would be a good issue for a first time contributor to undertake.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Issue Description
Podman does not generate events about network.
Steps to reproduce the issue
This works using docker, "docker events" returns :
2024-09-22T11:13:53.675328084+02:00 network create e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 (name=newnet, type=macvlan)
Thanks for feedback
Describe the results you received
No result
Describe the results you expected
2024-09-22T11:13:53.675328084+02:00 network create e8b293029385f147e18459e093bd5ac40226323ef2a28c504f16cad4f6b54278 (name=newnet, type=macvlan)
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: