Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker load cannot load xz archive files #5271

Closed
3 tasks done
mbengit opened this issue Jan 19, 2021 · 12 comments
Closed
3 tasks done

docker load cannot load xz archive files #5271

mbengit opened this issue Jan 19, 2021 · 12 comments

Comments

@mbengit
Copy link

mbengit commented Jan 19, 2021

Executing docker load < archive.xz on the command line produces this error:

exec: "xz": executable file not found in $PATH

This issue was introduced in Docker Desktop 3.1.0 and is easily reproducible on MacOS and Windows.

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID: 63F376B3-ACF5-425B-843D-AAED828D01E7/20210119170855
@mbengit
Copy link
Author

mbengit commented Jan 19, 2021

It seems likely that the new Debian container added in 3.1.0 does not support xz.

@stephen-turner
Copy link
Contributor

Yes, it could be that. @simonferquel PTAL.

@mbengit
Copy link
Author

mbengit commented Feb 3, 2021

Hi, is there any progress on a fix for this issue?
I work on a product which depends on being able to load an xz-archived image to the local docker registry, so this issue has a sizeable impact.

@mat007
Copy link
Member

mat007 commented Feb 10, 2021

Hi, the fix will be available in the next release.

@qalinn
Copy link

qalinn commented Feb 10, 2021

Hi @mat007,

Could you tell me when is planned the next release?
I am also impacted by this issue.

Thank you!

@stephen-turner
Copy link
Contributor

stephen-turner commented Feb 10, 2021

Sorry, we don't have a firm date yet, but it will probably be towards the end of this month.

@qalinn
Copy link

qalinn commented Feb 10, 2021

@stephen-turner That means days, weeks, months? Or how does it release a new version?

@stephen-turner
Copy link
Contributor

Definitely weeks, not days or months.

@qalinn
Copy link

qalinn commented Feb 10, 2021

@stephen-turner Thank you

@Djelibeybi
Copy link

As a workaround, you can use buildx and the default moby/buildkit:buildx-stable-1 image which appears to still hve xz in it, i.e.:

$ docker buildx create --driver docker-container --name fix-xz --use
$ docker buildx build --load -t image:tag .
[+] Building 30.5s (7/7) FINISHED
 => [internal] booting buildkit                                                                                                                                              12.7s
 => => pulling image moby/buildkit:buildx-stable-1                                                                                                                           11.9s
 => => creating container buildx_buildkit_fix-xz0                                                                                                                          0.8s
 => [internal] load build definition from Dockerfile                                                                                                                          0.0s
 => => transferring dockerfile: 174B                                                                                                                                          0.0s
 => [internal] load .dockerignore                                                                                                                                             0.0s
 => => transferring context: 2B                                                                                                                                               0.0s
 => [internal] load build context                                                                                                                                             1.6s
 => => transferring context: 24.40MB                                                                                                                                          1.6s
 => [1/1] ADD archive.tar.xz /                                                                                                                        3.6s
 => exporting to oci image format                                                                                                                                            12.2s
 => => exporting layers                                                                                                                                                       6.5s
 => => exporting manifest sha256:2f98ad89fba24c0424199b31a9bdfe9e68507da99747404750eff5dd7702036c                                                                             0.0s
 => => exporting config sha256:156d3cd0610c9bda95c92c50dbb72fd9bfded8596521fc99f91111e7b06af58c                                                                               0.0s
 => => sending tarball                                                                                                                                                        5.7s
 => importing to docker

@stephen-turner
Copy link
Contributor

This is fixed in versions 3.2.0 and 3.2.1. Closing the ticket now.

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Apr 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants