rynbrd/rigger-coreos

A CoreOS template for Rigger.

Rigger CoreOS Source

CoreOS image source for Rigger. Builds new style images with read-only /usr and btrfs. See the amd64-usr index for available image versions. Packer v0.6.1 is used to build the images.

Platforms

Currently two platforms are available: amazon-instance and virtualbox. Configuration may be provided through the sources.cfg file located at Rigger's root directory.

amazon-instance

Instance AMI's are created with two ephemeral disks. The first disk (xvda) is mounted as ROOT (/). The second disk (xvdb) is mounted as VAR (/var). Script and unit file modifications are made to accomplish this.

Ths following configuration options are necessary:

• AWS_ACCOUNT_ID - The account ID used to create the AMI.
• AWS_ACCESS_KEY - An access key for the above account.
• AWS_SECRET_KEY - The secret key associated with the access key.
• AWS_BUCKET - The bucket to store the AMI image in.

virtualbox

VirtualBox instances are created with a single 40GB disk. The disk may be extended from VirtualBox prior to booting. This will cause CoreOS to expend to the available space. The public key in files/virtualbox/id_rsa.pub is added to the authrized_keys file for the core user. Use the associated id_rsa file as the private key when connecting.

License

This software project is licensed under the BSD-derived license and is copyright (c) 2014 Ryan Bourgeois. A copy of the license is included in the LICENSE file. If it is missing then a copy may be found on the project page.

rigger-coreos's Issues

run 'provision' with 'bash' instead of 'sh'

This error:

    amazon-instance: 100% 12,701      --.-K/s   in 0s
    amazon-instance:
    amazon-instance: 2014-12-21 18:42:39 (60.2 MB/s) - ‘/tmp/coreos-install’ saved [12701/12701]
    amazon-instance:
    amazon-instance: /tmp/script.sh: 87: /tmp/script.sh: [[: not found

… is caused by provision being run by sh instead of bash. Changing the shebang to #!/bin/bashfixes that.

https://github.com/BlueDragonX/rigger-coreos/blob/4ae611e03f815452b9760f804c3329f12b8796b9/provision#L1

On some Linux distributions /bin/sh is no longer a symlink to /bin/bash.

Please make 'channel' configurable.

rigger-coreos currently only pulls from channel stable. It would be fantastic if users could change that.

Thanks!

package ec2-ami-tools is not available

With packer 0.6.1 I run into this error:

==> amazon-instance: Uploading files => /tmp/files
==> amazon-instance: Provisioning with shell script: provision
    amazon-instance: >> Provisioning for builder amazon-instance
    amazon-instance: -- Preparing tools ...
    amazon-instance: -- Preparing environment ...
…
    amazon-instance: Get:32 http://us-east-1.ec2.archive.ubuntu.com trusty-updates/universe Translation-en [117 kB]
    amazon-instance: Fetched 21.8 MB in 27s (790 kB/s)
    amazon-instance: Reading package lists... Done
    amazon-instance: Reading package lists... Done
    amazon-instance: Building dependency tree
    amazon-instance: Reading state information... Done
    amazon-instance: Package ec2-ami-tools is not available, but is referred to by another package.
    amazon-instance: This may mean that the package is missing, has been obsoleted, or
    amazon-instance: is only available from another source
    amazon-instance:
    amazon-instance: Package ec2-api-tools is not available, but is referred to by another package.
    amazon-instance: This may mean that the package is missing, has been obsoleted, or
    amazon-instance:
    amazon-instance: is only available from another source
    amazon-instance:
    amazon-instance: E: Package 'ec2-api-tools' has no installation candidate
    amazon-instance: E: Package 'ec2-ami-tools' has no installation candidate
==> amazon-instance: Terminating the source AWS instance...

I am a layman when it comes to Ubuntu, so I don't know what's the real cause. But, requesting packer 0.7.5 easily fixes that:

cd rigger
cd sources
git clone --depth=1 https://github.com/BlueDragonX/rigger-coreos.git
sed -i -e 's:0.6.1:0.7.5:g' rigger-coreos/configure
cd ..

---

Please note that downloading the new version fails, which is outside the scope of this bugreport. A workaround for now is:

mkdir -p .data/tmp
cd $_
wget -N https://dl.bintray.com/mitchellh/packer/packer_0.7.5_linux_amd64.zip
cd ../..

Or, even better:

mkdir -p .data/tmp
curl -z .data/tmp/packer_0.7.5_linux_amd64.zip -LR https://dl.bintray.com/mitchellh/packer/packer_0.7.5_linux_amd64.zip -o .data/tmp/packer_0.7.5_linux_amd64.zip