coreos

I cannot figure out from documentation and source code how to define size of the root device. You can specify N additional block devices using BlockDeviceMappings section where you can declare their sizes. But there is no way to set size of the root volume. So it always create an instance with root volume of size 8GB which is the default value. Ran into this issue myself today, probably to late for the original poster, but in case anyone else stumbles across this question later I did the following: import boto3 ec2 = boto3.resource('ec2', region_name='eu-west-1', aws_access_key_id='my-key',

I'm stumped. I'm trying to run a vagrant/virtualbox/coreos cluster on Windows 8.1 to develop the cluster for running in the cloud. I've tried this on four machines (all are Windows 8.1 with latest updates and all with the latest VirtualBox, Vagrant, Git, and the same config for Vagrant. I'm checking the Vagrant config out of a repo on all 4 system so I'm confident the configs are the same for each. I get 2 successes and 2 failures. Two machines succeed like this: Bringing machine 'core-01' up with 'virtualbox' provider... ==> core-01: Checking if box 'coreos-stable' is up to date... (snip)

What is the right way to set PATH variable in a systemd unit file? After seeing a few examples, I tried to use the format below, but the variable doesn't seem to expand. Environment="PATH=/local/bin:$PATH" I am trying this on CoreOS with the below version of systemd. systemd 225 -PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS -ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN You can't use EnvVars in Environment directives. The whole Environment= will be ignored. If you use EnvironmentFile= , then the specified file will be loaded without substitution.

So I have another follow-up question regarding installing a node.js-based framework under Docker on CoreOS, per this post . So, because npm is finicky about installing from package.json via root, I've had to create a nonroot sudo user in order to install the package. This is what my Dockerfile currently looks like inside of our repo, building off of an ubuntu image: # Install dependencies and nodejs RUN apt-get update RUN apt-get install -y python-software-properties python g++ make RUN add-apt-repository ppa:chris-lea/node.js RUN apt-get update RUN apt-get install -y nodejs # Install git RUN

I'm building a container cluster using CoreOs and Kubernetes on DigitalOcean, and I've seen that in order to expose a Pod to the world you have to create a Service with Type: LoadBalancer. I think this is the optimal solution so that you don't need to add external load balancer outside kubernetes like nginx or haproxy. I was wondering if it is possible to create this using DO's Floating IP. Robert Bailey The LoadBalancer type of service is implemented by adding code to the kubernetes master specific to each cloud provider. There isn't a cloud provider for Digital Ocean ( supported cloud

Docker 刚问世就红透半边天，不仅拿了融资，还得到了Google等巨头的支持。CoreOS此前一直忙于为 Docker 提供技术支持服务，似乎准备好好沾沾 Docker 的光，现在看来它另有一番打算：据gigaom.com的消息，昨天 CoreOS在Github上发布了一款容器引擎竞争产品原型Rocket，意在和 Docker 抢抢风头。 Rocket 是一款容器引擎，和 Docker 类似，帮助开发者打包应用和依赖包到可移植容器中，简化搭环境等部署工作。CoreOS 的 CEO Alex Polvi 在官方博文里介绍道，Rocket 和 Docker 不同的地方在于，Rocket 没有 Docker 那些为企业用户提供的“友好功能”，比如云服务加速工具、集群系统等。反过来说，Rocket 想做的，是一个更纯粹的业界标准。 Alex Polvi 认为，由于 Docker 貌似已经从原本做 " 业界标准容器 " 的初心转变成打造一款以容器为中心的企业服务平台，CoreOS 才决定开始推出自己的标准化产品。 CoreOS 把它的容器称为 App Containers，里面包含 app container image、runtime、container-discovery 协议等。其中，App Container Image 和 Docker 里的 Image 比较类似