-
Notifications
You must be signed in to change notification settings - Fork 353
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
box-cutter/ubuntu1610 not working #6
Comments
This repo has a fix for this.
…----------
On Thu, Nov 9, 2017 at 18:45, Revanth Reddy T <[email protected]> wrote:
Bringing machine 'm1' up with 'virtualbox' provider...
Bringing machine 'w1' up with 'virtualbox' provider...
Bringing machine 'w2' up with 'virtualbox' provider...
==> m1: Importing base box 'box-cutter/ubuntu1610'...
==> m1: Matching MAC address for NAT networking...
==> m1: Checking if box 'box-cutter/ubuntu1610' is up to date...
==> m1: Setting the name of the VM: swarm_m1_1510270504981_15294
==> m1: Clearing any previously set network interfaces...
==> m1: Preparing network interfaces based on configuration...
m1: Adapter 1: nat
m1: Adapter 2: bridged
==> m1: Forwarding ports...
m1: 22 (guest) => 2222 (host) (adapter 1)
==> m1: Running 'pre-boot' VM customizations...
==> m1: Booting VM...
==> m1: Waiting for machine to boot. This may take a few minutes...
m1: SSH address: 127.0.0.1:2222
m1: SSH username: vagrant
m1: SSH auth method: private key
m1:
m1: Vagrant insecure key detected. Vagrant will automatically replace
m1: this with a newly generated keypair for better security.
m1:
m1: Inserting generated public key within guest...
m1: Removing insecure key from the guest if it's present...
m1: Key inserted! Disconnecting and reconnecting using new SSH key...
==> m1: Machine booted and ready!
==> m1: Checking for guest additions in VM...
==> m1: Setting hostname...
==> m1: Configuring and enabling network interfaces...
==> m1: Mounting shared folders...
m1: /vagrant =>
/Users/revantht/Projects/Innominds/Mobilogix/innominds_mobilogix_server/infra/swarm
==> m1: Running provisioner: shell...
m1: Running:
/var/folders/t8/gv0q03sd7vz0m17qd6g33b0r0000gn/T/vagrant-shell20171110-36080-1eq72r9.sh
==> m1: # Executing docker install script, commit: 49ee7c1
==> 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/
==> m1: usermod: group 'docker' does not exist
==> m1: /tmp/vagrant-shell: line 13: /etc/docker/daemon.json: No such file
or directory
==> m1: --2017-11-09 23:35:34--
https://raw.githubusercontent.com/docker/docker/v17.05.0-ce/contrib/init/systemd/docker.service.rpm
==> m1: Resolving raw.githubusercontent.com (raw.githubusercontent.com)...
==> m1: 151.101.8.133
==> m1: Connecting to raw.githubusercontent.com (raw.githubusercontent.com
)|151.101.8.133|:443...
==> m1: connected.
==> m1: HTTP request sent, awaiting response...
==> m1: 200 OK
==> m1: Length:
==> m1: 1140
==> m1: (1.1K)
==> m1: [text/plain]
==> m1: Saving to: '/lib/systemd/system/docker.service'
==> m1:
==> m1: 0K
==> m1:
==> m1: .
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1: 100%
==> m1: 203M
==> m1: =0s
==> m1:
==> m1: 2017-11-09 23:35:35 (203 MB/s) -
'/lib/systemd/system/docker.service' saved [1140/1140]
==> m1: Job for docker.service failed because the control process exited
with error code.
==> m1: See "systemctl status docker.service" and "journalctl -xe" for
details.
==> m1: Reading package lists...
==> m1: Building dependency tree...
==> m1: E
==> m1: :
==> m1: Unable to locate package ipvsadm
==> m1: E
==> m1: :
==> m1: Unable to locate package tree
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAK_3fjWEFttFLsY2gWWYN9laLyiPTTwks5s046lgaJpZM4QY2sC>
.
|
Which repo you are talking about. 10 days back it worked but today it is not working |
box-cutter/ubuntu1610 is not able to run docker. Revanths-MacBook-Pro-2:swarm revantht$ export DOCKER_HOST=192.168.0.201 |
==> m1: Job for docker.service failed because the control process exited with error code. How to solve this issue? Please help me |
What’s the error code/message lead you to?
…----------
On Fri, Nov 10, 2017 at 17:24, Revanth Reddy T <[email protected]> wrote:
==> m1: Job for docker.service failed because the control process exited
with error code.
How to solve this issue? Please help me
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAK_3UZwzvh6jo_cBakx6N--0_XhMAukks5s1M0MgaJpZM4QY2sC>
.
|
can u help this ? Bringing machine 'm1' up with 'virtualbox' provider... Could not resolve host: cdn.boxcutter.io Could not resolve host: cdn.boxcutter.io |
Bringing machine 'm1' up with 'virtualbox' provider...
Bringing machine 'w1' up with 'virtualbox' provider...
Bringing machine 'w2' up with 'virtualbox' provider...
==> m1: Importing base box 'box-cutter/ubuntu1610'...
==> m1: Matching MAC address for NAT networking...
==> m1: Checking if box 'box-cutter/ubuntu1610' is up to date...
==> m1: Setting the name of the VM: swarm_m1_1510270504981_15294
==> m1: Clearing any previously set network interfaces...
==> m1: Preparing network interfaces based on configuration...
m1: Adapter 1: nat
m1: Adapter 2: bridged
==> m1: Forwarding ports...
m1: 22 (guest) => 2222 (host) (adapter 1)
==> m1: Running 'pre-boot' VM customizations...
==> m1: Booting VM...
==> m1: Waiting for machine to boot. This may take a few minutes...
m1: SSH address: 127.0.0.1:2222
m1: SSH username: vagrant
m1: SSH auth method: private key
m1:
m1: Vagrant insecure key detected. Vagrant will automatically replace
m1: this with a newly generated keypair for better security.
m1:
m1: Inserting generated public key within guest...
m1: Removing insecure key from the guest if it's present...
m1: Key inserted! Disconnecting and reconnecting using new SSH key...
==> m1: Machine booted and ready!
==> m1: Checking for guest additions in VM...
==> m1: Setting hostname...
==> m1: Configuring and enabling network interfaces...
==> m1: Mounting shared folders...
m1: /vagrant => /Users/revantht/Projects/Innominds/Mobilogix/innominds_mobilogix_server/infra/swarm
==> m1: Running provisioner: shell...
m1: Running: /var/folders/t8/gv0q03sd7vz0m17qd6g33b0r0000gn/T/vagrant-shell20171110-36080-1eq72r9.sh
==> m1: # Executing docker install script, commit: 49ee7c1
==> 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/
==> m1: usermod: group 'docker' does not exist
==> m1: /tmp/vagrant-shell: line 13: /etc/docker/daemon.json: No such file or directory
==> m1: --2017-11-09 23:35:34-- https://raw.githubusercontent.com/docker/docker/v17.05.0-ce/contrib/init/systemd/docker.service.rpm
==> m1: Resolving raw.githubusercontent.com (raw.githubusercontent.com)...
==> m1: 151.101.8.133
==> m1: Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.8.133|:443...
==> m1: connected.
==> m1: HTTP request sent, awaiting response...
==> m1: 200 OK
==> m1: Length:
==> m1: 1140
==> m1: (1.1K)
==> m1: [text/plain]
==> m1: Saving to: '/lib/systemd/system/docker.service'
==> m1:
==> m1: 0K
==> m1:
==> m1: .
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1:
==> m1: 100%
==> m1: 203M
==> m1: =0s
==> m1:
==> m1: 2017-11-09 23:35:35 (203 MB/s) - '/lib/systemd/system/docker.service' saved [1140/1140]
==> m1: Job for docker.service failed because the control process exited with error code.
==> m1: See "systemctl status docker.service" and "journalctl -xe" for details.
==> m1: Reading package lists...
==> m1: Building dependency tree...
==> m1: E
==> m1: :
==> m1: Unable to locate package ipvsadm
==> m1: E
==> m1: :
==> m1: Unable to locate package tree
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
The text was updated successfully, but these errors were encountered: