-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Final v2.0.5 backports #7402
Final v2.0.5 backports #7402
Commits on Aug 24, 2020
-
error when adding container to pod with network information
because a pod's network information is dictated by the infra container at creation, a container cannot be created with network attributes. this has been difficult for users to understand. we now return an error when a container is being created inside a pod and passes any of the following attributes: * static IP (v4 and v6) * static mac * ports -p (i.e. -p 8080:80) * exposed ports (i.e. 222-225) * publish ports from image -P Signed-off-by: Brent Baude <bbaude@redhat.com> <MH: Fixed cherry pick conflicts and compile> Signed-off-by: Matthew Heon <mheon@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 2325114 - Browse repository at this point
Copy the full SHA 2325114View commit details -
Ensure pod infra containers have an exit command
Most Libpod containers are made via `pkg/specgen/generate` which includes code to generate an appropriate exit command which will handle unmounting the container's storage, cleaning up the container's network, etc. There is one notable exception: pod infra containers, which are made entirely within Libpod and do not touch pkg/specgen. As such, no cleanup process, network never cleaned up, bad things can happen. There is good news, though - it's not that difficult to add this, and it's done in this PR. Generally speaking, we don't allow passing options directly to the infra container at create time, but we do (optionally) proxy a pre-approved set of options into it when we create it. Add ExitCommand to these options, and set it at time of pod creation using the same code we use to generate exit commands for normal containers. Fixes containers#7103 Signed-off-by: Matthew Heon <mheon@redhat.com> <MH: Fixed cherry-pick conflicts> Signed-off-by: Matthew Heon <mheon@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 484bd0a - Browse repository at this point
Copy the full SHA 484bd0aView commit details -
Clean up pods before returning from Pod Stop API call
This should help alleviate races where the pod is not fully cleaned up before subsequent API calls happen. Signed-off-by: Matthew Heon <mheon@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for c572378 - Browse repository at this point
Copy the full SHA c572378View commit details -
Final release notes update for v2.0.5.
Really. I promise. No more after this. Signed-off-by: Matthew Heon <mheon@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 884355c - Browse repository at this point
Copy the full SHA 884355cView commit details -
HACK: Manually include c/storage containers#698
We need this release out by end of day, so we don't have time to do this right. Disable the vendor task and manually add c/storage PR containers#698 to the vendored copy of c/storage to make the tests pass. Once containers#698 merges into c/storage, we need to remove this commit and backport it to the v1.20 stable branch, then cut a release there. Signed-off-by: Matthew Heon <mheon@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for ae2ee65 - Browse repository at this point
Copy the full SHA ae2ee65View commit details -
Configuration menu - View commit details
-
Copy full SHA for 776abc5 - Browse repository at this point
Copy the full SHA 776abc5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 13d5b2d - Browse repository at this point
Copy the full SHA 13d5b2dView commit details