https://github.com/taraspos/bootstrap-coreos

bootstrap script for coreos
https://github.com/taraspos/bootstrap-coreos

Last synced: 23 days ago
JSON representation

bootstrap script for coreos

• Host: GitHub
• URL: https://github.com/taraspos/bootstrap-coreos
• Owner: taraspos
• Created: 2015-06-08T12:39:52.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2015-06-24T14:25:37.000Z (over 9 years ago)
• Last Synced: 2024-01-09T14:45:43.154Z (10 months ago)
• Language: Shell
• Size: 271 KB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## [HOW-TO Create Bootable flesh Drive on Windows](https://github.com/Trane9991/bootstrap-coreos/wiki/HOW-TO-Create-Bootable-flesh-Drive-on-WIndows) ##

## [HOW-TO VirtualBox CoreOS VM](https://github.com/Trane9991/bootstrap-coreos/wiki/VirtualBox-create-CoreOS-VM) ##

## HOW-TO Use bootstarp.sh script ##

To use this script you need to inject it into CoreOS installation ISO(**isomaster** tool on Ubuntu) and write it to the flesh drive(**unetbootin**) or use customized ISO as virtual CD in the VirtualBox or VMware

When you booted form Installation ISO(on the bare-metal on VM) you need to do next steps:

* Mount flesh drive or virtual CD partition:

```

sudo mount /dev/sdb1 /mnt/ ## if you installing from Flash Drive

```  

or

```

sudo mount /dev/sr0 /mnt/ ## if you installing from virtual CD in VirtualBox

```

* Run script with **SUDO** replacing *CLIENT_ID* with real value.

```

sudo bash /mnt/bootstrap.sh CLIENT_ID

```

**NOTE:** if you didn't specify *CLIENT_ID* as script parameter you will be asked for input during script runtime

To use your own cloud-config files replace ```CLOUD_INIT_REPOSITORY``` variable. All cloud-config files should be named like ```cloud-config-CLIENT_ID```, where *CLIENT_ID* is real value.

* During script runtime you will be asked for Login into your QUAY.io account. To change Docker private repository supplier change ```DOCKER_PRIVARE_REPOSITORY``` value

**NOTE**: sometime during login step CoreOS can prompt some unexpected output, just ignore it and keep typing username.

* Pull out Flesh Drive or Virtual CD (in case of VirtualBox VM):

 ![virtual_cd](http://img.ctrlv.in/img/15/06/23/55898d58a8a70.jpg)

* Reboot when everything is done and login with credentials which are specified in choosen cloud-config file

## USE EXAMPLE ##

```

sudo mount /dev/sr0 /mnt                    #### Installing on VirtualBox

sudo bash /mnt/bootstrap.sh proxy-DHCP      #### cloud-config-proxy-DHCP from templates directory

##### aking for input to login in quay.io

username

password

email

#####

sudo reboot

```

This script will do next things:

* Install CoreOS

* Add downloaded cloud-config file in the */var/lib/coreos-install* directory, so it will be executed after reboot

* LogIn into quay.io account  (just example of login, in the cloud-config templates all docker containers pulling from public repositories)

* Set hostname equal *core-CLIENT_ID*

* Create user **adminaccount** with **qwer1234** password and SUDO access

* Configure such proxy address: http_proxy=http://10.128.225.206:8080

* Configure DHCP networking

* Pull all containers specified in the cloud-config file(*nginx* and *cAdvisor* in this case) so they will be available after reboot

**NOTE:** username, password, proxy, networking, containers - all this values are in the cloud-config file and can be changed in case of need

## Templates ##

* *cloud-config-proxy-DHCP, cloud-config-proxy-static and cloud-config-noproxy-static* require to set proper **network interface**, **ip address**, **default gateway** , **proxy_url**

* Login step is just example, all docker containers pulling from public repositories