engine: amend 23.0 release notes with tracking issues for known issues

Signed-off-by: Bjorn Neergaard <bneergaard@mirantis.com>
This commit is contained in:
Bjorn Neergaard 2023-02-02 22:39:55 -07:00
parent f1bf8b03fc
commit 48e0158f4f
No known key found for this signature in database
1 changed files with 2 additions and 2 deletions

View File

@ -219,7 +219,7 @@ For a full list of pull requests and changes in this release, refer to the relev
### Known issues ### Known issues
#### apparmor_parser #### apparmor_parser ([tracking issue](https://github.com/moby/moby/issues/44900))
Some Debian users have reported issues with containers failing to start after upgrading to the 23.0 branch. Some Debian users have reported issues with containers failing to start after upgrading to the 23.0 branch.
The error message indicates that the issue is due to a missing `apparmor_parser` binary: The error message indicates that the issue is due to a missing `apparmor_parser` binary:
@ -236,7 +236,7 @@ The workaround to this issue is to install the `apparmor` package manually:
apt-get install apparmor apt-get install apparmor
``` ```
#### Kata Containers #### Kata Containers ([tracking issue](https://github.com/kata-containers/kata-containers/issues/6154))
The 23.0 branch brings support for alternate containerd shims, such as `io.containerd.runsc.v1` (gVisor) and `io.containerd.kata.v2` (Kata Containers). The 23.0 branch brings support for alternate containerd shims, such as `io.containerd.runsc.v1` (gVisor) and `io.containerd.kata.v2` (Kata Containers).