Description of problem: Upstream released new version https://github.com/moby/moby/releases/tag/v20.10.17 Could we please kick off builds?
FEDORA-2022-016be11a81 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-016be11a81
FEDORA-2022-016be11a81 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-1d955acf8c has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1d955acf8c
FEDORA-2022-2b9205baf6 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-2b9205baf6
FEDORA-2022-cea20dae0b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-cea20dae0b
FEDORA-2022-3ecd21576a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3ecd21576a
FEDORA-2022-3ecd21576a has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-3ecd21576a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3ecd21576a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-cea20dae0b has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-cea20dae0b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-cea20dae0b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-cea20dae0b has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-3ecd21576a has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.