Skip to content
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

Release 1.0.2 #3149

Closed
kolyshkin opened this issue Aug 11, 2021 · 4 comments · Fixed by #3173
Closed

Release 1.0.2 #3149

kolyshkin opened this issue Aug 11, 2021 · 4 comments · Fixed by #3173
Milestone

Comments

@kolyshkin
Copy link
Contributor

kolyshkin commented Aug 11, 2021

Here are PRs that we need in order to release 1.0.2:

I hope to make a release ASAP (as k8s issue, kubernetes/kubernetes#104280) is quite nasty.

Release notes draft

This is a second stable release in 1.0 branch, fixing a few medium and high
priority issues, including one that affect Kubernetes using runc's libcontainer.

Bugfixes:

 - Fixed a failure to set CPU quota period in some cases on cgroup v1. (#3115)
 - Fixed the inability to start a container with the "adding seccomp filter
   rule for syscall ..." error, caused by redundant seccomp rules (i.e. those
   that has action equal to the default one). Such redundant rules are now
   skipped. (#3129)
 - Made release builds reproducible from now on. (#3142)
 - Fixed a rare debug log race in runc init, which can result in occasional
   harmful "failed to decode ..." errors from runc run or exec. (#3130)
 - Fixed the check in cgroup v1 systemd manager if a container needs to be
   frozen before Set, and add a setting to skip such freeze unconditionally.
   The previous fix for that issue, done in  runc 1.0.1, was not working.
   (#3167)

@kolyshkin kolyshkin added this to the 1.0.2 milestone Aug 11, 2021
@odinuge
Copy link
Contributor

odinuge commented Aug 12, 2021

Thanks for working on this, and being so quick about the release @kolyshkin! 🙌

@cyphar
Copy link
Member

cyphar commented Aug 20, 2021

If that's everything @kolyshkin I'll prepare the release PR now?

@cyphar cyphar linked a pull request Aug 20, 2021 that will close this issue
@AkihiroSuda
Copy link
Member

I guess we could bump up Go 1.17 (#3021), but can be postponed to v1.0.3.

@cyphar
Copy link
Member

cyphar commented Aug 23, 2021

@cyphar cyphar closed this as completed Aug 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants