{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":290188301,"defaultBranch":"main","name":"common","ownerLogin":"Luap99","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2020-08-25T10:47:34.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/45212748?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1715864872.0","currentOid":""},"activityList":{"items":[{"before":"ee0734fae41d708315f767a2dece6211fb435007","after":"fca82ba7f18f1b1bb496c8df8e3ebc828a2cc607","ref":"refs/heads/rootlessnetns-info","pushedAt":"2024-05-16T13:24:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork: add option to return rootless-netns ips\n\nWhen using the bridge network mode as rootless we use the rootless netns\nlogic, for podman this looks like just as using bridge as root. The\nissue is however due the extra namespace we block certain address there.\nThis can be seen best with pasta but actually effects other cases too.\nThe podman logic tries to use any host ip address for\nhost.containers.internal but we must make sure to exculde all these\naddress in the rootless netns as they are not actually the hostns as\nthus cause great confusion.\n\nFor the --network pasta case I already fixed this by returning the ips on\nthe pasta.Setup2() call in b809d7231132.\nFor the bridge mode this more complicated due several layers of function\ncalls. I decided to implement this as extra function call on the interface\nto return the ips as this makes the usage in podman the easiest. And I\nalso didn't want to break the API as we only have to fix this in podman\nnot buildah.\n\nIt is needed to address #22653 but it needs podman changes as well to\nuse this new function.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork: add option to return rootless-netns ips"}},{"before":"5bd9dee54d6cb857cfececdebde5dab1bc9fb2a4","after":"ee0734fae41d708315f767a2dece6211fb435007","ref":"refs/heads/rootlessnetns-info","pushedAt":"2024-05-16T13:10:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork: add option to return rootless-netns ips\n\nWhen using the bridge network mode as rootless we use the rootless netns\nlogic, for podman this looks like just as using bridge as root. The\nissue is however due the extra namespace we block certain address there.\nThis can be seen best with pasta but actually effects other cases too.\nThe podman logic tries to use any host ip address for\nhost.containers.internal but we must make sure to exculde all these\naddress in the rootless netns as they are not actually the hostns as\nthus cause great confusion.\n\nFor the --network pasta case I already fixed this by returning the ips on\nthe pasta.Setup2() call in b809d7231132.\nFor the bridge mode this more complicated due several layers of function\ncalls. I decided to implement this as extra function call on the interface\nto return the ips as this makes the usage in podman the easiest. And I\nalso didn't want to break the API as we only have to fix this in podman\nnot buildah.\n\nIt is needed to address #22653 but it needs podman changes as well to\nuse this new function.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork: add option to return rootless-netns ips"}},{"before":"10ffb79057387f6da34de125166c11f719ec5765","after":"5bd9dee54d6cb857cfececdebde5dab1bc9fb2a4","ref":"refs/heads/rootlessnetns-info","pushedAt":"2024-05-16T13:08:48.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork: Add option ro return rootless-netns ips\n\nWhen using the bridge network mode as rootless we use the rootless netns\nlogic, for podman this looks like just as using bridge as root. The\nissue is however due the extra namespace we block certain address there.\nThis can be seen best with pasta but actually effects other cases too.\nThe podman logic tries to use any host ip address for\nhost.containers.internal but we must make sure to exculde all these\naddress in the rootless netns as they are not actually the hostns as\nthus cause great confusion.\n\nFor the --network pasta case I already fixed this by returning the ips on\nthe pasta.Setup2() call in b809d7231132.\nFor the bridge mode this more complicated due several layers of function\ncalls. I decided to implement this as extra function call on the interface\nto return the ips as this makes the usage in podman the easiest. And I\nalso didn't want to break the API as we only have to fix this in podman\nnot buildah.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork: Add option ro return rootless-netns ips"}},{"before":null,"after":"10ffb79057387f6da34de125166c11f719ec5765","ref":"refs/heads/rootlessnetns-info","pushedAt":"2024-05-16T13:07:52.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork: Add option ro return rootless-netns ips\n\nWhen using the bridge network mode as rootless we use the rootless netns\nlogic, for podman this looks like just as using bridge as root. The\nissue is however due the extra namespace we block certain address there.\nThis can be seen best with pasta but actually effects other cases too.\nThe podman logic tries to use any host ip address for\nhost.containers.internal but we must make sure to exculde all these\naddress in the rootless netns as they are not actually the hostns as\nthus cause great confusion.\n\nFor the --network pasta case I already fixed this by returing the ips on\nthe pasta.Setup2() call in b809d7231132.\nFor the brisge mode this more complicated due several layers of function\ncalls. I decided to implement this as extra function call on the interface\nto return the ips as this makes the usage in podman the easiest. And I\nalso didn't want to break the API as we only have to fix this in podman\nnot buildah.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork: Add option ro return rootless-netns ips"}},{"before":"c0378d9773a8ec413b61eafb9aecc4aab0f0b13d","after":"019cb750a797257e8ba63ca6a858d66037e0c15c","ref":"refs/heads/dnsname-test","pushedAt":"2024-05-15T16:29:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"CI: update VM to fedora 40\n\nAlso removes the podman-plugins (dnsname) package.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"CI: update VM to fedora 40"}},{"before":null,"after":"c0378d9773a8ec413b61eafb9aecc4aab0f0b13d","ref":"refs/heads/dnsname-test","pushedAt":"2024-05-15T16:26:21.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"CI: update VM to fedora 40\n\nAlso removes the podman-plugins (dnsname) package.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"CI: update VM to fedora 40"}},{"before":"917c5837ee41dd63303d43cc4a23b9f0bb359ca3","after":null,"ref":"refs/heads/map-gw","pushedAt":"2024-04-26T08:57:52.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"}},{"before":"11d833b521e8414090cd982a246324d17c32d227","after":null,"ref":"refs/heads/docker-26","pushedAt":"2024-04-25T17:38:01.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"}},{"before":"6b44fc7426b730ed36d8ab270eb6c71eed635d45","after":"11d833b521e8414090cd982a246324d17c32d227","ref":"refs/heads/docker-26","pushedAt":"2024-04-25T14:18:38.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"Fix missing build tag for c/storage\n\nWe do not have a new c/storage here so we still try to use devicemapper\nby default in the lint task, make sure it is disabled.\n\nThis got broken after commit cd7e39eba2 which remove the dep from the\ninstall.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"Fix missing build tag for c/storage"}},{"before":"b35aaba8bca2822cc93d82fedf4963e2b7b23b33","after":"6b44fc7426b730ed36d8ab270eb6c71eed635d45","ref":"refs/heads/docker-26","pushedAt":"2024-04-25T13:39:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"vendor: update module github.com/docker/docker to v26\n\nFor some reason the renovate PR does incorrect vendoring:\nhttps://github.com/containers/common/pull/1925\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"vendor: update module github.com/docker/docker to v26"}},{"before":null,"after":"b35aaba8bca2822cc93d82fedf4963e2b7b23b33","ref":"refs/heads/docker-26","pushedAt":"2024-04-25T13:34:36.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"vendor: update module github.com/docker/docker to v26\n\nFor some reason the renovate PR does incorrect vendoring:\nhttps://github.com/containers/common/pull/1925\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"vendor: update module github.com/docker/docker to v26"}},{"before":"3261227b01456c2cf0a1a0ff28daadf534c67fb4","after":"917c5837ee41dd63303d43cc4a23b9f0bb359ca3","ref":"refs/heads/map-gw","pushedAt":"2024-04-25T13:07:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork/pasta: fix multiple --map-gw parsing\n\nIt is possible for a user to set --map-gw more than once so we should\nhandle it correctly.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork/pasta: fix multiple --map-gw parsing"}},{"before":"b41b411ef63205d93d09ea07bdf89422337f82a4","after":"3261227b01456c2cf0a1a0ff28daadf534c67fb4","ref":"refs/heads/map-gw","pushedAt":"2024-04-25T13:05:53.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork/pasta: fix multiple --map-gw parsing\n\nIt is possible for a user to set --map-gw more than once so we shoud\nhandle it correctly.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork/pasta: fix multiple --map-gw parsing"}},{"before":null,"after":"b41b411ef63205d93d09ea07bdf89422337f82a4","ref":"refs/heads/map-gw","pushedAt":"2024-04-25T13:05:09.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork/pasta: fix multiple --map-gw parsing\n\nIt is possible for a user to set --map-gw more than once so we shoud\nhandle it correctly.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork/pasta: fix multiple --map-gw parsing"}},{"before":"8e7d37fbd13a32b3d6e5a3eeedeaed2766f09efc","after":null,"ref":"refs/heads/pasta-args","pushedAt":"2024-04-25T09:20:05.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"}},{"before":"c7568505e342e0ae0a8323d791b09da8e39ed4d9","after":"8e7d37fbd13a32b3d6e5a3eeedeaed2766f09efc","ref":"refs/heads/pasta-args","pushedAt":"2024-04-24T13:40:25.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork/pasta: fix --map-gw parsing\n\nIf a port option was given after --map-gw then parsing failed as the\nnext arg was always skipped due the modification of the slice.\n\nModifing the slice inside the loop is bad and does not do what some\nmight think. Append here basically creates a new slice (thus you always\nhave to assign the result to the variable) with the same pointer to the\nsame underlying array of data[1]. The loop however will still continue to\nloop over the slice as it saw it at the begining of the loop.\n\nSo in the bug case the underlying array would look like this:\n{\"--config-net\", \"--map-gw\", \"-T\", \"80\"}\nand after the append call to remove --map-gw like this:\n{\"--config-net\", \"-T\", \"80\", \"80\"}\n\nThe loop iterator has no idea this happen and just moves to the next\nindex 2 (\"80\") and thus we never passed \"-T\" causing this bug.\n\n[1] https://go.dev/blog/slices-intro\n\nFixes containers/podman#22477\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork/pasta: fix --map-gw parsing"}},{"before":null,"after":"c7568505e342e0ae0a8323d791b09da8e39ed4d9","ref":"refs/heads/pasta-args","pushedAt":"2024-04-24T11:57:38.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork/pasta: fix --map-gw parsing\n\nIf a port option was given after --map-gw then parsing failed as the\nnext arg was always skipped due the modification of the slice.\n\nModifing the slice inside the loop is bad and does not do what some\nmight think. Append here basically creates a new slice (thus you always\nhave to assign the result to the variable) with the same pointer to the\nsame underlying array of data[1]. The loop however will still continue to\nloop over the slice as it saw it at the begining of the loop.\n\nSo in the bug case the underlying array would look like this:\n{\"--config-net\", \"--map-gw\", \"-T\", \"80\"}\nand after the append call to remove --map-gw like this:\n{\"--config-net\", \"-T\", \"80\", \"80\"}\n\nThe loop iterator has no idea this happen and just moves to the next\nindex 2 (\"80\") and thus we never passed \"-T\" causing this bug.\n\n[1] https://go.dev/blog/slices-intro\n\nFixes containers/podman#22477\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork/pasta: fix --map-gw parsing"}},{"before":"71117d8194154c9620cfd24f9aa16d72ce7455e2","after":null,"ref":"refs/heads/go1.21","pushedAt":"2024-04-22T18:20:23.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"}},{"before":"c5bc984ce85f95ea5851b952498737d4e9f5ce89","after":"71117d8194154c9620cfd24f9aa16d72ce7455e2","ref":"refs/heads/go1.21","pushedAt":"2024-04-22T12:13:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"Replace golang.org/x/exp/slices with slices from std\n\nUse \"slices\" from the standard library, this package was added in go\n1.21 so we can use it now.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"Replace golang.org/x/exp/slices with slices from std"}},{"before":null,"after":"c5bc984ce85f95ea5851b952498737d4e9f5ce89","ref":"refs/heads/go1.21","pushedAt":"2024-04-22T12:09:29.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"Replace golang.org/x/exp/slices with slices from std\n\nUse \"slices\" from the standard library, this package was added in go\n1.21 so we can use it now.\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"Replace golang.org/x/exp/slices with slices from std"}},{"before":"0585a906dcd5d4dc7a3362276e1d9501d54b977b","after":null,"ref":"refs/heads/helper-bin-error","pushedAt":"2024-04-22T11:31:02.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"}},{"before":"ead8bddbad08b53b21e4e04a1fdc53da4935a63e","after":null,"ref":"refs/heads/healthcheck-event","pushedAt":"2024-04-19T15:05:17.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"}},{"before":null,"after":"0585a906dcd5d4dc7a3362276e1d9501d54b977b","ref":"refs/heads/helper-bin-error","pushedAt":"2024-04-18T15:40:21.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"pkg/config: fix FindHelperBinary() error message\n\nThe error message currently includes the full attributedstring.Slice\nstruct which looks wrong and can confuse users. Make sure we actually\nshow the list of directories.\n\nFixes 82e88cc97c (\"pkg/config: use NewSlice, Get and Set where possible\")\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"pkg/config: fix FindHelperBinary() error message"}},{"before":null,"after":"ead8bddbad08b53b21e4e04a1fdc53da4935a63e","ref":"refs/heads/healthcheck-event","pushedAt":"2024-04-17T14:24:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"pkg/config: add new healthcheck_events field\n\nSome users wish to turn of healthcheck events in Podman so add a config\noption to allow that. The actual logic must live in Podman.\n\nLink: https://issues.redhat.com/browse/RHEL-18987\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"pkg/config: add new healthcheck_events field"}},{"before":"135830286d6f5a9a93e474fae78a7784c3a0d1ea","after":null,"ref":"refs/heads/0.58-backports","pushedAt":"2024-04-15T13:59:59.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"}},{"before":"206edae115612d658f21c72de0777260343b4e40","after":null,"ref":"refs/heads/nv-ipam","pushedAt":"2024-04-12T16:11:37.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"}},{"before":null,"after":"135830286d6f5a9a93e474fae78a7784c3a0d1ea","ref":"refs/heads/0.58-backports","pushedAt":"2024-04-12T16:11:01.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork/netavark: remove ipam bucket on network rm\n\nThis is good to prevent any leaks but more important here there is a\nbug because we cache the last assigned ip. However when a network is\nremoved the recreated with a different LeaseRange that ip might be very\nwell outside the expected range and the logic seems to handle this\ncorrectly. I could fix it there but deleting the full bucket seems best\nas it avoid other issues and leaking the bucket forever.\n\nFixes containers/podman#22034\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork/netavark: remove ipam bucket on network rm"}},{"before":"121a68720b76f5c85841acaffd45013c5be045f5","after":"206edae115612d658f21c72de0777260343b4e40","ref":"refs/heads/nv-ipam","pushedAt":"2024-04-03T16:20:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork/netavark: remove ipam bucket on network rm\n\nThis is good to prevent any leaks but more important here there is a\nbug because we cache the last assigned ip. However when a network is\nremoved the recreated with a different LeaseRange that ip might be very\nwell outside the expected range and the logic seems to handle this\ncorrectly. I could fix it there but deleting the full bucket seems best\nas it avoid other issues and leaking the bucket forever.\n\nFixes containers/podman#22034\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork/netavark: remove ipam bucket on network rm"}},{"before":"83d08eaefea905580157b0dc281f018b04151e76","after":"121a68720b76f5c85841acaffd45013c5be045f5","ref":"refs/heads/nv-ipam","pushedAt":"2024-04-03T16:19:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork/netavark: remove ipam bucket on network rm\n\nThis is first good tp prevent any leaks but more important here there is\na bug because we cache the last assigned ip. However when a network is\nremoved the recreated with a different LeaseRange that ip might be very\nwell outside the expected range and the logic seems to handle this\ncorrectly. I could fix it there but deleting the full bucket seems best\nas it avoid other issues and leaking the bucket forever.\n\nFixes containers/podman#22034\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork/netavark: remove ipam bucket on network rm"}},{"before":"9101827de7cd3f5527ea8987fbaff2f3e107ded2","after":"83d08eaefea905580157b0dc281f018b04151e76","ref":"refs/heads/nv-ipam","pushedAt":"2024-04-03T16:18:07.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Luap99","name":"Paul Holzinger","path":"/Luap99","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45212748?s=80&v=4"},"commit":{"message":"libnetwork/netavark: remove ipam bucket on network rm\n\nThis is first good tp prevent any leaks but more important here there is\na bug because we cache the last assigned ip. However when a network is\nremoved the recreated with a different LeaseRange that ip might be very\nwell outside the expected range and the logic seems to handle this\ncorrectly. I could fix it there but deleting the full bucket seems best\nas it avoid other issues and leaking the bucket forever.\n\nFixes containers/podman#22034\n\nSigned-off-by: Paul Holzinger <pholzing@redhat.com>","shortMessageHtmlLink":"libnetwork/netavark: remove ipam bucket on network rm"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAES6jQCQA","startCursor":null,"endCursor":null}},"title":"Activity · Luap99/common"}