Excluded layers not pushed to repository on Docker Desktop after PR#294 #296
Description
Hi team,
After deploying the changes introduced by PR #294 , we've encountered an issue related to Docker image operations.
Specifically, when using docker push for an image saved via the routine modified in this commit, the Docker daemon (with the default "use containerd storage" option enabled) does not push the layers excluded during the save operation to the repository.
This subsequently causes docker pull operations to fail on nodes that don't already have the excluded layers locally present.
We've observed that disabling the "Use containerd for pulling and storing images" option in the Docker Desktop before performing the save operation resolves the problem. However, as this option is enabled by default, this solution feels like a temporary workaround rather than the ideal fix.
I wanted to report this behavior to see if others have experienced similar issues or if this interaction between the commit's changes, docker save, and containerd storage might be unintentional. Any insights or guidance would be greatly appreciated!
Thanks.