From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: moby: update to 20.10.21.
Date: Thu, 24 Nov 2022 21:18:32 +0100 [thread overview]
Message-ID: <20221124201832.odnGpvFp7QrUThLd7iFrG_TA6ycQI_YYcqheISHbAfI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40484@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
There's a merged pull request on the void-packages repository
moby: update to 20.10.21.
https://github.com/void-linux/void-packages/pull/40484
Description:
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl (crossbuild)
- armv7l (crossbuild)
- armv6l-musl (crossbuild)
docker was updates to 20.10.21 but the docker server (moby) is still on 20.10.17. Also I found out that btrfs >= 5.19 as a storage driver is only supported by the newer version.
In the future it would make sense to update moby together with the other docker packages.
prev parent reply other threads:[~2022-11-24 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 13:32 [PR PATCH] " dataCobra
2022-11-13 10:06 ` [PR PATCH] [Updated] " dataCobra
2022-11-16 12:22 ` dataCobra
2022-11-17 12:50 ` [PR REVIEW] " paper42
2022-11-17 12:50 ` paper42
2022-11-22 10:14 ` [PR PATCH] [Updated] " dataCobra
2022-11-24 15:41 ` dataCobra
2022-11-24 15:42 ` [PR REVIEW] " dataCobra
2022-11-24 15:43 ` dataCobra
2022-11-24 18:20 ` thypon
2022-11-24 18:30 ` paper42
2022-11-24 19:30 ` [PR PATCH] [Updated] " dataCobra
2022-11-24 19:30 ` [PR REVIEW] " dataCobra
2022-11-24 20:18 ` paper42 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221124201832.odnGpvFp7QrUThLd7iFrG_TA6ycQI_YYcqheISHbAfI@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).