An open-source, in-house service platform with a PaaS-like workflow, built on Docker, CoreOS, Etcd and Fleet. This repository houses the documentation and installation scripts.
$ ./integration.sh
Starting Paz integration test script
Checking for existing Vagrant cluster
Creating a new Vagrant cluster
Cloning into 'coreos-vagrant'...
fatal: unable to access 'https://github.com/coreos/coreos-vagrant/': Could not resolve host: github.com
../scripts/helpers.sh: line 35: cd: coreos-vagrant: Not a directory
Can't open config.rb.sample: No such file or directory.
A Vagrant environment or target machine is required to run this
command. Run `vagrant init` to create a new Vagrant environment. Or,
get an ID of a target machine from `vagrant global-status` to run
this command on. A final option is to change to a directory with a
Vagrantfile and to try again.
A Vagrant environment or target machine is required to run this
command. Run `vagrant init` to create a new Vagrant environment. Or,
get an ID of a target machine from `vagrant global-status` to run
this command on. A final option is to change to a directory with a
Vagrantfile and to try again.
Waiting for Vagrant cluster to be ready...
CoreOS Vagrant cluster is up
mkdir: unitfiles: File exists
cp: ../unitfiles/*: No such file or directory
mkdir: scripts: File exists
cp: ../scripts/start-runlevel.sh: No such file or directory
...and so on. Should just be a matter of adding -e to the shebang line in integration.sh.
...and so on. Should just be a matter of adding
-eto the shebang line inintegration.sh.