You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been experiencing issues in Moby v23.0.2 that are consistent with docker/buildx#1325. Should #3493 also be backported to v0.10.x for use in Moby v23.0.2+x?
The text was updated successfully, but these errors were encountered:
To help reduce the confusion; the v0.10.7 is a pseudo-version generated by Go modules (they pick "latest tag found" and increment the vx.y.z patch version.
The "version" here is the commit-sha at the end (70f2ad5 in this case)
I'm trying to determine if the latest release of Docker (
v23.0.2
) is still impacted by docker/buildx#1325.This issue was resolved with #3493 and backported to
v0.11
in #3540.In the latest release,
docker/moby
pulls inv0.10.7-0.20230306143919-70f2ad56d3e5
. (Note:v0.10.7
auto-generated by Go, see #3770 (comment)).We have been experiencing issues in Moby
v23.0.2
that are consistent with docker/buildx#1325. Should #3493 also be backported tov0.10.x
for use in Mobyv23.0.2+x
?The text was updated successfully, but these errors were encountered: