docker-swarm-mode-getting-started
docker-swarm-mode-getting-started copied to clipboard
box-cutter/ubuntu1610 cannot be retrieved
Hi,
I tried to do vagrant up today or manually add the box and I could do it. I get the menu to choose the provider, but I cannot download the box.
So vagrantfile is no working.
What's the error output from vagrant?
What provider are you using? Is it listed here? https://app.vagrantup.com/box-cutter/boxes/ubuntu1610
It is listed. But there is no file at that link.
[image: Inline images 1]
On 27 November 2017 at 16:21, Wes Higbee [email protected] wrote:
What's the error output from vagrant?
What provider are you using? Is it listed here? https://app.vagrantup.com/box-cutter/boxes/ubuntu1610
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/g0t4/docker-swarm-mode-getting-started/issues/3#issuecomment-347235030, or mute the thread https://github.com/notifications/unsubscribe-auth/AApIHIePx26TqCAUXG6udB9xHLgwiSHbks5s6uFwgaJpZM4QroXM .
I'd inquire with box-cutter
On Mon, Nov 27, 2017 at 12:16 PM, mladenuzelac [email protected] wrote:
It is listed. But there is no file at that link.
[image: Inline images 1]
On 27 November 2017 at 16:21, Wes Higbee [email protected] wrote:
What's the error output from vagrant?
What provider are you using? Is it listed here? https://app.vagrantup.com/box-cutter/boxes/ubuntu1610
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/g0t4/docker-swarm-mode-getting- started/issues/3#issuecomment-347235030>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ AApIHIePx26TqCAUXG6udB9xHLgwiSHbks5s6uFwgaJpZM4QroXM> .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/g0t4/docker-swarm-mode-getting-started/issues/3#issuecomment-347254420, or mute the thread https://github.com/notifications/unsubscribe-auth/AAK_3fwNuT7jpcoseKN_J3Cs8119sSrcks5s6u5xgaJpZM4QroXM .
It seems that they don't host preloaded images
https://github.com/boxcutter/ubuntu Current Boxes
We no longer provide pre-built binaries for these templates.
And there is no 1610 box to build. It seems that your repo needs to be updated.
Regards, Mladen.
On 27 November 2017 at 22:29, Wes Higbee [email protected] wrote:
I'd inquire with box-cutter
On Mon, Nov 27, 2017 at 12:16 PM, mladenuzelac [email protected] wrote:
It is listed. But there is no file at that link.
[image: Inline images 1]
On 27 November 2017 at 16:21, Wes Higbee [email protected] wrote:
What's the error output from vagrant?
What provider are you using? Is it listed here? https://app.vagrantup.com/box-cutter/boxes/ubuntu1610
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/g0t4/docker-swarm-mode-getting- started/issues/3#issuecomment-347235030>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ AApIHIePx26TqCAUXG6udB9xHLgwiSHbks5s6uFwgaJpZM4QroXM> .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/g0t4/docker-swarm-mode-getting- started/issues/3#issuecomment-347254420>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAK_3fwNuT7jpcoseKN_ J3Cs8119sSrcks5s6u5xgaJpZM4QroXM> .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/g0t4/docker-swarm-mode-getting-started/issues/3#issuecomment-347350519, or mute the thread https://github.com/notifications/unsubscribe-auth/AApIHNlDfV3p1YWnKZeEu8ajIk-eLpJ0ks5s6zfjgaJpZM4QroXM .
Is that for boxcutter or box-cutter?
On Thu, Nov 30, 2017 at 05:45, mladenuzelac [email protected] wrote:
It seems that they don't host preloaded images
https://github.com/boxcutter/ubuntu Current Boxes
We no longer provide pre-built binaries for these templates.
And there is no 1610 box to build. It seems that your repo needs to be updated.
Regards, Mladen.
On 27 November 2017 at 22:29, Wes Higbee [email protected] wrote:
I'd inquire with box-cutter
On Mon, Nov 27, 2017 at 12:16 PM, mladenuzelac [email protected] wrote:
It is listed. But there is no file at that link.
[image: Inline images 1]
On 27 November 2017 at 16:21, Wes Higbee [email protected] wrote:
What's the error output from vagrant?
What provider are you using? Is it listed here? https://app.vagrantup.com/box-cutter/boxes/ubuntu1610
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/g0t4/docker-swarm-mode-getting- started/issues/3#issuecomment-347235030>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ AApIHIePx26TqCAUXG6udB9xHLgwiSHbks5s6uFwgaJpZM4QroXM> .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/g0t4/docker-swarm-mode-getting- started/issues/3#issuecomment-347254420>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAK_3fwNuT7jpcoseKN_ J3Cs8119sSrcks5s6u5xgaJpZM4QroXM> .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/g0t4/docker-swarm-mode-getting-started/issues/3#issuecomment-347350519 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AApIHNlDfV3p1YWnKZeEu8ajIk-eLpJ0ks5s6zfjgaJpZM4QroXM
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/g0t4/docker-swarm-mode-getting-started/issues/3#issuecomment-348151896, or mute the thread https://github.com/notifications/unsubscribe-auth/AAK_3dCLzEeZuLVDH_xgihnveSP_nEvxks5s7odmgaJpZM4QroXM .
Tried changing to 1604, getting the same...
` C:\Projects\docker-swarm-mode-getting-started>vagrant up Bringing machine 'm1' up with 'virtualbox' provider... Bringing machine 'm2' up with 'virtualbox' provider... Bringing machine 'm3' up with 'virtualbox' provider... Bringing machine 'w1' up with 'virtualbox' provider... Bringing machine 'w2' up with 'virtualbox' provider... Bringing machine 'w3' up with 'virtualbox' provider... Bringing machine 'w4' up with 'virtualbox' provider... ==> m1: Box 'box-cutter/ubuntu1604' could not be found. Attempting to find and install... m1: Box Provider: virtualbox m1: Box Version: >= 0 ==> m1: Loading metadata for box 'box-cutter/ubuntu1604' m1: URL: https://vagrantcloud.com/box-cutter/ubuntu1604 ==> m1: Adding box 'box-cutter/ubuntu1604' (v2.0.26) for provider: virtualbox m1: Downloading: https://vagrantcloud.com/box-cutter/boxes/ubuntu1604/versions/2.0.26/providers/virtualbox.box m1: An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again.
The requested URL returned error: 404 Not Found `
Tried instead generic/ubuntu1610. The box got downloaded fine (altho, very slow), but then the provisioning failed on docker installation script:
m1: # Executing docker install script, commit: 1d31602 m1: m1: Either your platform is not easily detectable or is not supported by this m1: installer script. m1: Please visit the following URL for more detailed installation instructions: m1: m1: https://docs.docker.com/engine/installation/
it's boxcutter, they moved from box-cutter to boxcutter on github. Either way, they no longer provide the binaries so the box doesn't work and cannot be downloaded. This a show stopper for me just now as I go through the course. Does anyone know where I can find an alternate box to download, or can explain what needs to be done to a generic Ubuntu box to make this work? Is it just a case of installing virtualbox (or your desired provider) onto it?
I'll post this on vagrant cloud under my own account.
ndn-jenkins/ubuntu1604-amd64
This one might do the trick instead!
EDIT: Have tested using this Vagrant box and it works nicely.
Tried ndn-jenkins/ubuntu1604-amd64 but got the following error:
m1: Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again.
OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
Using Ecodev/ubuntu-server-1604 worked for me
Hello!
So, it looks like we still have this issue?!?? Would it be possible to update the vagrant file with an image that are downloadable and and the provisioning script works with? I have tried changing images to download, "generic/ubuntu1610" and so on. no luck so far..
Cheers, Fred
Still experiencing this problem.