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

The box 'boxcutter/centos72-docker' could not be found #2379

Closed
Pacoies opened this issue Sep 7, 2016 · 8 comments
Closed

The box 'boxcutter/centos72-docker' could not be found #2379

Pacoies opened this issue Sep 7, 2016 · 8 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Milestone

Comments

@Pacoies
Copy link

Pacoies commented Sep 7, 2016

I am following instructions from https://www.eclipse.org/che/getting-started/download/ to install Eclipse Che using vagrant in OS X El Capitán

  1. mkdir che
  2. Download Vagrantfile from https://github.com/eclipse/che/blob/master/Vagrantfile to che/
  3. cd che/
  4. vagrant up

Receive error message:

The box 'boxcutter/centos72-docker' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
vagrant login. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/boxcutter/centos72-docker"]
Error: The requested URL returned error: 404 Not Found

I have browsed https://atlas.hashicorp.com/boxcutter and I cannot find any other xxxx-docker box to put in the Vagrantfile.

Any hint? :-)

@TylerJewell
Copy link

TylerJewell commented Sep 8, 2016

@paco-cruz-iesbelen - grumble. It does seem that this particular docker image has been removed. We'll need to revamp the Dockerfile to use a base image and we'll do a fresh install of Docker into it.

If you don't mind me asking - is there value in the Vagrant image for Che? Given that we have the Che launcher which launches it as a docker container, isn't that approach even simpler? Would it make sense for us to consider phasing out the Vagrantfile approach and only supporting the Docker container approach?

@TylerJewell TylerJewell added kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Sep 8, 2016
@TylerJewell TylerJewell added this to the 4.7.2 milestone Sep 8, 2016
@humb1t
Copy link

humb1t commented Sep 8, 2016

@paco-cruz-iesbelen catch it config.vm.box = "andrewhk/centos72-docker"

@Pacoies
Copy link
Author

Pacoies commented Sep 8, 2016

@TylerJewell the value for me is simple human laziness :-)

I happen to have vagrant already installed, someone passed me a link and I tried the easiest route, that's all.

Nevertheless, the image from @humb1t is up and running OK.

@Pacoies
Copy link
Author

Pacoies commented Sep 8, 2016

@humb1t the image is up and running OK. Thanks a lot! :-)

@Pacoies Pacoies closed this as completed Sep 8, 2016
@Pacoies Pacoies reopened this Sep 8, 2016
@Pacoies
Copy link
Author

Pacoies commented Sep 8, 2016

I was thinking that perhaps it would be appropriate to either edit the page at https://www.eclipse.org/che/getting-started/download/ and remove the reference to vagrant, or to update http://github.com/eclipse/che/blob/master/Vagrantfile with a correct image to avoid others getting the same error I had.

@Pacoies Pacoies closed this as completed Sep 8, 2016
@TylerJewell TylerJewell reopened this Sep 8, 2016
@TylerJewell
Copy link

The issue needs to remain open as other users will encounter the problem. We are tempted to remove Vagrant installation entirely - and only support Docker installation approach. It's cleaner and faster.

@TylerJewell
Copy link

PR to fix: #2388. Also requires 4.7.1 which has a critical bug fix about running Che in a container while inside of a VM. 4.7.1 release will happen within the next 24 hours.

@TylerJewell
Copy link

Fixed and merged - 4.7.2 was released this morning.

@TylerJewell TylerJewell self-assigned this Sep 9, 2016
@bmicklea bmicklea mentioned this issue Sep 9, 2016
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Development

No branches or pull requests

3 participants