-
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
Bump to v4.0.0-RC5 #13203
Bump to v4.0.0-RC5 #13203
Conversation
Revert containers#13049. criu-3.16.1-6.fc36 fixes the problem and is now in fc36 stable: https://bodhi.fedoraproject.org/updates/FEDORA-2022-183b337712 (Yes, I confirmed that tests pass on a rawhide vm) Signed-off-by: Ed Santiago <[email protected]>
separated cgroupNS sharing from setting the pod as the cgroup parent, made a new flag --share-parent which sets the pod as the cgroup parent for all containers entering the pod remove cgroup from the default kernel namespaces since we want the same default behavior as before which is just the cgroup parent. resolves containers#12765 Signed-off-by: cdoern <[email protected]> Signed-off-by: cdoern <[email protected]> Signed-off-by: cdoern <[email protected]>
Append the podman dns seach domain to the host search domains when we use the dnsname/aardvark server. Previously it would only use podman seach domains and discard the host domains. Fixes containers#13103 Signed-off-by: Paul Holzinger <[email protected]>
Bumps [github.com/buger/goterm](https://github.com/buger/goterm) from 1.0.1 to 1.0.4. - [Release notes](https://github.com/buger/goterm/releases) - [Commits](buger/goterm@v1.0.1...v1.0.4) --- updated-dependencies: - dependency-name: github.com/buger/goterm dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
foramtError was written as err [NO NEW TESTS NEEDED] Signed-off-by: myml <[email protected]>
It seems we are ignoring output from healthcheck session. Open a valid pipe to healthcheck session in order read its output. Use common pipe for both `stdout/stderr` since that was the previous behviour as well. Signed-off-by: Aditya R <[email protected]>
All the healthcheck return output now but systems tests is written to expect empty output which seems wrong. Modify jq output to contain newline character rather than actual newline Signed-off-by: Aditya R <[email protected]>
Followup to containers#13129: remove a no-longer-necessary workaround for a healthcheck bug. Signed-off-by: Ed Santiago <[email protected]>
…son in reponse Lot of clients are expecting proper `Content-type: application/json` configured in response headers of `/build` compat api. Following commit fixes that. Fixes issues where code is setting header field after writing header which is wrong. We must set `content-type` before we write and flush http header. Signed-off-by: Aditya R <[email protected]>
When running podman inside systemd user units, it is possible that systemd kills the rootless netns slirp4netns process because it was started in the default unit cgroup. When the unit is stopped all processes in that cgroup are killed. Since the slirp4netns process is run once for all containers it should not be killed. To make sure systemd will not kill the process we move it to the user.slice. Fixes containers#13153 Signed-off-by: Paul Holzinger <[email protected]>
'killContainerTimeout' is already 5 second [NO NEW TESTS NEEDED] Signed-off-by: myml <[email protected]>
Signed-off-by: Tom Deseyn <[email protected]>
Right now it is not possible to look at the API version for a specific version. docs.podman.io always show the latest version from the main branch. This is not want many users want so they now have the ability to select a different version. Fixes containers#12796 Signed-off-by: Paul Holzinger <[email protected]>
I do not know why this code was added but it is wrong. We should never use a plugin dir as config dir. Also this will fail for netavark. The correct default will be set in c/common so podman should not touch it. [NO NEW TESTS NEEDED] Ref containers#13183 Signed-off-by: Paul Holzinger <[email protected]>
The `podman network connect` and `podman network disconnect` commands give containers access to different networks than the ones they were created with; these networks can also have DNS servers associated with them. Until now, however, we did not modify resolv.conf as network membership changed. With this PR, `podman network connect` will add any new nameservers supported by the new network to the container's /etc/resolv.conf, and `podman network disconnect` command will do the opposite, removing the network's nameservers from `/etc/resolv.conf`. Fixes containers#9603 Signed-off-by: Matthew Heon <[email protected]>
Signed-off-by: Matthew Heon <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
We might want to hold this up untile @lsm5 Figures out containers/storage#1131 |
I'll leave this open to let CI bake, but I'm fine waiting for that to get resolved. |
API unit tests are failing, on a test that seems to validate that the current version is compatible with the API. This makes me think the bump to v4.0.0 as the minimum is conflicting with the v4.0.0-dev version set. |
The api test are hard coded for v3.1,see Line 22 in 6d2b54a
|
@Luap99 That's the APIv2 tests - the unit tests are failing very differently. |
Specifically podman/pkg/api/handlers/utils/handler_test.go Lines 14 to 54 in 29d7ab3
|
Signed-off-by: Matthew Heon <[email protected]>
Signed-off-by: Matthew Heon <[email protected]>
Three failures in |
It's all manifest changes. I don't think I did any backports that would affect that code? |
I'm going to restart just one of the tests, in the hopes that it was transitory; if that passes we're probably OK. |
Nope, failures are consistent. OK... |
It's all manifest failures. Nearest I can tell there are no manifest-related changes in this PR, either to code or tests. I'm going to get another PR pushed to try and verify. |
I don't know how, but bumping minimum API version breaks the Libpod API manifest endpoints. I want to debug this, but it's Friday afternoon, so I'm going to vote that we release the RC now and debug later. |
CI is barfing and this seems like the most likely cause. Signed-off-by: Matthew Heon <[email protected]>
One flake (I hope...) - restarted |
Another flake. Restarted. |
Ready |
/lgtm |
Also includes associated release notes updates and backports