search

moby / moby

The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
https://mobyproject.org/
Apache License 2.0
68.77k stars 18.67k forks source link

Boot2docker can't unpack images from index.docker.io #3952

Closed ruphin closed 10 years ago

ruphin commented 10 years ago

I just installed docker 0.8 and the latest boot2docker from the OSX installation instructions.

When attempting to pull repositories from index.docker.io (during container build), it crashes with the following error:

Error pulling image (0.9.1) from phusion/baseimage, exit status 1: xz: invalid option -- 'q' BusyBox v1.21.1 (2013-12-27 18:04:45 UTC) multi-call binary.

and finally:

build: pull: Could not find repository on any of the indexed registries.

After quick inspection I found that the 'xz' binary used in boot2docker does not support the 'q' option, causing this error.

scottbessler commented 10 years ago

This is likely an issue for https://github.com/steeve/boot2docker/issues

scottbessler commented 10 years ago

I opened an issue over there: https://github.com/steeve/boot2docker/issues/130

ruphin commented 10 years ago

I noticed, thanks.

I realised this is a boot2docker issue, but since docker now 'officially' supports OS X, and this pretty much renders building anything on OS X impossible, I thought it would be a docker issue as well. Seeing that the boot2docker issue list doesn't receive much traffic, I decided to post it on the docker list instead.

We'll see how fast it is resolved. I cannot wait to test some deployments on OS X, as it would be a great improvement to our development environment.

Phusion | Ruby & Rails deployment, scaling and tuning solutions

Web: http://www.phusion.nl/ E-mail: goffert@phusion.nl

On Thu, Feb 6, 2014 at 1:18 AM, Scott Bessler notifications@github.comwrote:

I opened an issue over there: steeve/boot2docker#130https://github.com/steeve/boot2docker/issues/130

Reply to this email directly or view it on GitHubhttps://github.com/dotcloud/docker/issues/3952#issuecomment-34278602 .

unclejack commented 10 years ago

This has been fixed in boot2docker 0.5.3.