Skip to content

Instantly share code, notes, and snippets.

@kikitux
Last active August 29, 2015 14:07
Show Gist options
  • Save kikitux/d37b67c6a8dd1a76656e to your computer and use it in GitHub Desktop.
Save kikitux/d37b67c6a8dd1a76656e to your computer and use it in GitHub Desktop.
make fedora-atomic issue
rm -f fedora-atomic-virtualbox.box
rm -rf box/output-virtualbox/
virtualbox output will be in this color.
Warnings for build 'virtualbox':

* A checksum type of 'none' was specified. Since ISO files are so big,
a checksum is highly recommended.

==> virtualbox: Downloading or copying ISO
 virtualbox: Downloading or copying: file:///Volumes/hd1/Dropbox/work/packer-vagrant/fedora-atomic-packer/boot.iso
==> virtualbox: Starting HTTP server on port 8542
==> virtualbox: Creating virtual machine...
==> virtualbox: Creating hard drive...
==> virtualbox: Creating forwarded port mapping for SSH (host port 3029)
==> virtualbox: Executing custom VBoxManage commands...
 virtualbox: Executing: modifyvm fedora-atomic --memory 1024
==> virtualbox: Starting the virtual machine...
==> virtualbox: Waiting 5s for boot...
==> virtualbox: Typing the boot command...
==> virtualbox: Waiting for SSH to become available...
==> virtualbox: Connected to SSH!
==> virtualbox: Uploading VirtualBox version info (4.3.16)
==> virtualbox: Uploading ../oem/ => /tmp
==> virtualbox: Provisioning with shell script: /var/folders/zg/dw2mgnh135l9976wfs62tsmh0000gp/T/packer-shell152081342
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: /tmp/script.sh: line 13: cd: /opt/bin: No such file or directory
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
 virtualbox: : syntax error near line 1 <<<
 virtualbox: : syntax error near line 2 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 3 <<<
 virtualbox: : syntax error near line 4 <<<
 virtualbox: : syntax error near line 5 <<<
 virtualbox: near line 1
 virtualbox: sudo: no valid sudoers sources found, quitting
 virtualbox: sudo: unable to initialize policy plugin
==> virtualbox: Unregistering and deleting virtual machine...
==> virtualbox: Deleting output directory...
Build 'virtualbox' errored: Script exited with non-zero exit status: 1
==> Some builds didn't complete successfully and had errors:
--> virtualbox: Script exited with non-zero exit status: 1
==> Builds finished but no artifacts were created.
rm -f fedora-atomic-virtualbox.box
rm -rf box/output-virtualbox/
virtualbox output will be in this color.
Warnings for build 'virtualbox':

* A checksum type of 'none' was specified. Since ISO files are so big,
a checksum is highly recommended.

==> virtualbox: Downloading or copying ISO
 virtualbox: Downloading or copying: file:///Volumes/hd1/Dropbox/work/packer-vagrant/fedora-atomic-packer/boot.iso
==> virtualbox: Starting HTTP server on port 8705
==> virtualbox: Creating virtual machine...
==> virtualbox: Creating hard drive...
==> virtualbox: Creating forwarded port mapping for SSH (host port 2371)
==> virtualbox: Executing custom VBoxManage commands...
 virtualbox: Executing: modifyvm fedora-atomic --memory 1024
==> virtualbox: Starting the virtual machine...
==> virtualbox: Waiting 5s for boot...
==> virtualbox: Typing the boot command...
==> virtualbox: Waiting for SSH to become available...
==> virtualbox: Connected to SSH!
==> virtualbox: Uploading VirtualBox version info (4.3.16)
==> virtualbox: Uploading ../oem/ => /tmp
==> virtualbox: Provisioning with shell script: /var/folders/zg/dw2mgnh135l9976wfs62tsmh0000gp/T/packer-shell833471990
 virtualbox: Created symlink from /etc/systemd/system/sockets.target.wants/docker-tcp.socket to /etc/systemd/system/docker-tcp.socket.
 virtualbox: Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
 virtualbox: Created symlink from /etc/systemd/system/sysinit.target.wants/systemd-machine-id-setup.service to /etc/systemd/system/systemd-machine-id-setup.service.
 virtualbox: dd: error writing ‘EMPTY’: No space left on device
 virtualbox: 34726+0 records in
 virtualbox: 34725+0 records out
 virtualbox: 36412657664 bytes (36 GB) copied, 290.624 s, 125 MB/s
==> virtualbox: Gracefully halting virtual machine...
==> virtualbox: Preparing to export machine...
 virtualbox: Deleting forwarded port mapping for SSH (host port 2371)
==> virtualbox: Exporting virtual machine...
 virtualbox: Executing: export fedora-atomic --output output-virtualbox/fedora-atomic.ovf
==> virtualbox: Unregistering and deleting virtual machine...
==> virtualbox: Running post-processor: vagrant
==> virtualbox (vagrant): Creating Vagrant box for 'virtualbox' provider
 virtualbox (vagrant): Copying from include: docker_start_service.rb
 virtualbox (vagrant): Copying from include: change_host_name.rb
 virtualbox (vagrant): Copying from include: configure_networks.rb
 virtualbox (vagrant): Copying from include: network_static.erb
 virtualbox (vagrant): Copying from artifact: output-virtualbox/fedora-atomic-disk1.vmdk
 virtualbox (vagrant): Copying from artifact: output-virtualbox/fedora-atomic.ovf
 virtualbox (vagrant): Renaming the OVF to box.ovf...
 virtualbox (vagrant): Using custom Vagrantfile: vagrantfile.tpl
 virtualbox (vagrant): Compressing: Vagrantfile
 virtualbox (vagrant): Compressing: box.ovf
 virtualbox (vagrant): Compressing: change_host_name.rb
 virtualbox (vagrant): Compressing: configure_networks.rb
 virtualbox (vagrant): Compressing: docker_start_service.rb
 virtualbox (vagrant): Compressing: fedora-atomic-disk1.vmdk
 virtualbox (vagrant): Compressing: metadata.json
 virtualbox (vagrant): Compressing: network_static.erb
Build 'virtualbox' finished.
==> Builds finished. The artifacts of successful builds are:
--> virtualbox: VM files in directory: output-virtualbox
--> virtualbox: 'virtualbox' provider box: ../fedora-atomic-virtualbox.box
==> box: Adding box 'fedora-atomic' (v0) for provider:
box: Downloading: file:///Volumes/hd1/Dropbox/work/packer-vagrant/fedora-atomic-packer/fedora-atomic-virtualbox.box
 box: Progress: 0% (Rate: 0/s, Estimated time remaining: --:--:--)  box: Progress: 2% (Rate: 409M/s, Estimated time remaining: --:--:--) ==> box: Successfully added box 'fedora-atomic' (v0) for 'virtualbox'!
==> fedora-atomic-test: VM not created. Moving on...
Bringing machine 'fedora-atomic-test' up with 'virtualbox' provider...
==> fedora-atomic-test: Importing base box 'fedora-atomic'...
Progress: 20% Progress: 30% Progress: 50% Progress: 90% ==> fedora-atomic-test: Matching MAC address for NAT networking...
==> fedora-atomic-test: Setting the name of the VM: test_fedora-atomic-test_1413704946451_70034
==> fedora-atomic-test: Clearing any previously set network interfaces...
==> fedora-atomic-test: Preparing network interfaces based on configuration...
fedora-atomic-test: Adapter 1: nat
fedora-atomic-test: Adapter 2: hostonly
==> fedora-atomic-test: Forwarding ports...
fedora-atomic-test: 2375 => 2375 (adapter 1)
fedora-atomic-test: 8080 => 8080 (adapter 1)
fedora-atomic-test: 22 => 2222 (adapter 1)
==> fedora-atomic-test: Running 'pre-boot' VM customizations...
==> fedora-atomic-test: Booting VM...
==> fedora-atomic-test: Waiting for machine to boot. This may take a few minutes...
fedora-atomic-test: SSH address: 127.0.0.1:2222
fedora-atomic-test: SSH username: vagrant
fedora-atomic-test: SSH auth method: private key
fedora-atomic-test: Warning: Connection timeout. Retrying...
==> fedora-atomic-test: Machine booted and ready!
==> fedora-atomic-test: Setting hostname...
==> fedora-atomic-test: Configuring and enabling network interfaces...
==> fedora-atomic-test: Running provisioner: docker...
fedora-atomic-test: Configuring Docker to autostart containers...
==> fedora-atomic-test: Pulling Docker images...
==> fedora-atomic-test: -- Image: yungsang/busybox
==> fedora-atomic-test: Pulling repository yungsang/busybox
==> fedora-atomic-test: Starting Docker containers...
==> fedora-atomic-test: -- Container: simple-echo
-----> /etc/os-release
NAME=Fedora
VERSION="22 (Rawhide)"
ID=fedora
VERSION_ID=22
PRETTY_NAME="Fedora 22 (Rawhide)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:22"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=Rawhide
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=Rawhide
Connection to 127.0.0.1 closed.
-----> /etc/redhat-release
Fedora release 22 (Rawhide)
Connection to 127.0.0.1 closed.
-----> /etc/oem-release
ID=fedora-atomic
NAME="Fedora Atomic box for Vagrant"
VERSION_ID=1.1.2
HOME_URL="https://vagrantcloud.com/yungsang/fedora-atomic"
SUPPORT_URL="https://github.com/YungSang/fedora-atomic-packer"
BUG_REPORT_URL="https://github.com/YungSang/fedora-atomic-packer/issues"
Connection to 127.0.0.1 closed.
-----> /etc/machine-id
45a5733b1ccb4486a8325cbc1f384df4
Connection to 127.0.0.1 closed.
-----> /etc/hostname
fedora-atomic-test
Connection to 127.0.0.1 closed.
-----> docker version
/bin/sh: docker: command not found
-----> docker images -t
/bin/sh: docker: command not found
-----> docker ps -a
/bin/sh: docker: command not found
-----> nc localhost 8080
hello world!
-----> atomic status
TIMESTAMP (UTC) ID OSNAME REFSPEC
* 2014-10-19 06:12:58 bb56cbbc3c fedora-atomic fedora-atomic:fedora-atomic/rawhide/x86_64/docker-host
Connection to 127.0.0.1 closed.
-----> atomic upgrade
Updating from: fedora-atomic:fedora-atomic/rawhide/x86_64/docker-host
78
No updates available.
Connection to 127.0.0.1 closed.
-----> docker-enter `sudo docker ps -l -q` ls -l
nsenter --target 3215 --mount --uts --ipc --net --pid -- ls -l
total 48
drwxrwxr-x 2 root root 4096 May 22 23:24 bin
drwxr-xr-x 4 root root 340 Oct 19 07:49 dev
drwxr-xr-x 6 root root 4096 Oct 19 07:49 etc
drwxrwxr-x 4 root root 4096 May 22 23:25 home
drwxrwxr-x 2 root root 4096 May 22 23:24 lib
lrwxrwxrwx 1 root root 3 May 22 23:02 lib64 -> lib
lrwxrwxrwx 1 root root 11 May 22 23:22 linuxrc -> bin/busybox
drwxrwxr-x 2 root root 4096 Feb 27 2014 media
drwxrwxr-x 2 root root 4096 Feb 27 2014 mnt
drwxrwxr-x 2 root root 4096 Feb 27 2014 opt
dr-xr-xr-x 112 root root 0 Oct 19 07:49 proc
drwx------ 2 root root 4096 Feb 27 2014 root
lrwxrwxrwx 1 root root 3 Feb 27 2014 run -> tmp
drwxr-xr-x 2 root root 4096 May 22 23:24 sbin
dr-xr-xr-x 13 root root 0 Oct 19 07:49 sys
drwxrwxrwt 3 root root 4096 May 22 23:24 tmp
drwxrwxr-x 6 root root 4096 May 22 23:24 usr
drwxrwxr-x 4 root root 4096 May 22 23:25 var
Connection to 127.0.0.1 closed.
==> fedora-atomic-test: Saving VM state and suspending execution...
virtualbox: near line 1
virtualbox: sudo: no valid sudoers sources found, quitting
virtualbox: sudo: unable to initialize policy plugin
real 14m26.198s
user 0m35.223s
sys 0m10.166s
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment