5 ms·

CoreOS Vagrant Images

125 points by NSMeta 13y ago

gchaix 13y ago
Who put containers in my Vagrant!?
- deleted 13y ago
  [deleted]
polvi 13y ago
Alex from CoreOS here: This only supports virtualbox at the moment, but we are actively working on adding VMware. Fill out the form on this page if you want us to spam you when we have the vmware image (or others): http://coreos.com/ http://coreos.com/
- OafTobark 13y ago
  Any plans for Parallels?
  - polvi 13y ago
    Not at the moment. That said, we will be publishing raw images that should be portable to just about anything.
  - turboroot 13y ago
    Vagrant supports VMWare, but not Parallels yet.
    - akulbe 13y ago
      Oh? I just tried to get one with the instructions on their github page, and it said the box type was vbox. Are the vmware versions kept elsewhere?
      - hoverbear 13y ago
        He was talking about Vagrant (the tool CoreOS uses to distribute VM images)... Also, I think you can just make a directory in the `~/vagrant.d/boxes/coreos` folder called "vmware" and copy over the vagrant file, box.ovf and the metadata.json. Then you just edit the metadata to have a vmware provider and the box.ovf to reference "../virtualbox/<<theimage>>" I however do not have a vagrant vmware license and cannot test this theory.
      - akulbe 13y ago
        Wow. I got voted down for this? You guys are great. :/
- runarb 13y ago
  Why no VMware, Xen or Qemu? We can help you if you have any issues with making thus work you know :)
makerops 13y ago
You guys really should change the logo to a cookie, every time I see the url I think of oreos.
- 2mur 13y ago
  I was thinking it should be a chewed on apple core, but now I cannot unsee the oreos... so I vote cookie logo too! Cool project
  - Aldo_MX 13y ago
    How about a chewed oreo?
WestCoastJustin 13y ago
To anyone wanting to learn more about Vagrant via a screencast, I've created one @ http://sysadmincasts.com/episodes/4-vagrant http://sysadmincasts.com/episodes/4-vagrant
ChikkaChiChi 13y ago
Vagrant for the uninformed: Headless interface to VirtualBox and VMWare VMs on OSX. Instancing is made a breeze.
- liamk 13y ago
  ChikkaChiChi, that may be the single best explanation for what Vagrant is. Most people answer: "It provisions VMs" which isn't as enlightening as your answer!
- DigitalJack 13y ago
  It isn't specific to osx is it?
  - jtreminio 13y ago
    It is not! Works on Linux, Mac and Windows.
- radioact1ve 13y ago
  Very good and simple explanation though I'd add Linux and Windows in there too.
passfree 13y ago
This is not related to the Vagrant<->CoreOS topic but since Vagrant box image format is a packaged ovf image it shouldn't be too hard to port the CoreOS images to Vortex (https://github.com/websecurify/node-vortex https://github.com/websecurify/node-vortex).
damm 13y ago
Ahh another Gentoo distro. Never ceases to amaze me how people troll it and yet it keeps popping out in every nook and cranny. https://github.com/coreos/coreos-overlay/ https://github.com/coreos/coreos-overlay/ Must have been a good idea that no one got.
- wmf 13y ago
  AFAIK CoreOS is based on ChromeOS which uses some parts from Gentoo. That doesn't mean Gentoo was ever a good idea for general-purpose PCs or servers.
  - damm 13y ago
    Nice burn on Gentoo. I've had the job of supporting Gentoo on a PaaS and have deployed it many places happily. Sadly one of the dumbest arguments ever that will blacken the Linux horizon for decades, big dick syndrome over what Linux distro you run.
    - vertex-four 13y ago
      Where can I find the page which guarantees me that any given version of any given package will be fully supported by a defined security team for security fixes for at least 2 years from release, preferably 3+? That is my argument against using Gentoo. I have absolutely no idea how long any given piece of it will be supported. If you can point me to a resource which explains that, I might take another look. I also have no interest in picking and choosing packages out of a bucket - I want a stable, well-defined OS that I can build on, and preferably one which is as close to what everyone else is using as possible so I can ask for help from people who understand my OS. Yes, it might work out if you're running at scale, have specialised needs, and can dedicate resources to what essentially amounts to development of a forked distro. It doesn't work out for me, as I need to know that the system I'm building isn't going to be unsupported in a couple of months, and I need to know I can talk to someone who is running similar versions of everything I'm running if everything goes wrong.
      - 13y ago
hosay123 13y ago
I don't want to sound overly negative, but attempting to support every useful combination of hardware and drivers, particularly in any kind of supported, certified configuration, ultimately leads back to the same result: just running a real OS. You can look at CoreOS the same way as the Xen hypervisor and VMWare ESX: the more flexible these became (new hardware drivers, supported configurations, etc. etc) the more they began to look like general purpose operating systems. At which point, why not start with one? (Kvm followed the same logic) I'd much rather see the guts of CoreOS available as e.g. a RHEL or Debian package. As it stands, throwing away 20 years of distribution experience just to avoid installing a few files on my server seems far from worth it.
- devinus 13y ago
  You just described the actual draw of CoreOS. CoreOS is just Linux. Instead of going the Xen route you just described, it can capitalize on being just Linux by supporting everything Linux already supports. At this point, you can view CoreOS, which is just Linux, as the "hypervisor." Containers don't have to replicate key subsystems in every paravirtualized instance, as containers share all the same subsystems like e.g. the TCP/IP stack. You're also not throwing away any distribution experience. Want CentOS? Create a CentOS container with Docker. Want Ubuntu? Create an Ubuntu container with Docker. These are incredibly powerful ideas I'm just now being exposed to.
  - hosay123 13y ago
    Try telling your SAN vendor that you're running "just Linux" and can you have a driver and support package for that please, and let us know how you get on. When you're done there, now try plugging your nice new machine into the corporate DC. Oh it seems it needs to support VLAN tagging. No problem, better just write some new code for that. Time to migrate a bunch of performance sensitive services. Uh oh, no support for FusionIO PCI SSDs! Better write some more code. Time to migrate your remote sites, only policy dictates certain services must be physically encrypted. No problem, better just cutpaste Debian's cryptsetup scripts and be done with it. Oops, turns out we deployed 1000 machines with a duff BIOS setting. No problem, I'm sure the server vendor has a support package for CoreOS.. We could come up with examples until we've basically reinvented a modern Redhat/Debian initramdisk and boot environment.
amalag 13y ago
Simple question, but if there is no package management, how do you install basic programs? Download binaries for everything?
- ceejayoz 13y ago
  I believe it's intended to be a minimal OS for running containers like those made by Docker (http://www.docker.io/ http://www.docker.io/).
- devinus 13y ago
  Simple answer: you don't. Longer answer: It depends. Do you want to use yum or apt-get to install programs? If you like CentOS, create a CentOS container with Docker and begin installing programs using yum! Ubuntu? Spool up an Ubuntu container and apt-get away! CoreOS is just the cradle upon which you can run the userland of any distribution you please.
  - amalag 13y ago
    So CoreOS is the simple host OS, thank you for the clarification, i thought it was a minimal guest OS.
hcarvalhoalves 13y ago
What's the idea behind CoreOS? I found the site incredibly weak in information about what it is.
- devinus 13y ago
  I've just begun looking into and playing with CoreOS. Basically, it's a minimal Linux image with Docker, service discovery using the `etcd` daemon they've written in Go, and several interesting properties. The most interesting is their use of the ChromiumOS build tools, allowing them to one day update servers the same way e.g. ChromeOS is updated--using the Omaha protocol to push raw binary diffs of the new root FS.
tbe 13y ago
This reminds me of Bedrock Linux, which allows you to run multiple linux distros on a single kernel instance. It does so using good old chroot, but has an implementation that is capable of breaking out of the chroot when entering a new one. This way the different environments become more integrated in that a RHEL binary can call a Debian binary and so on, creating a sort of super distro which is itself quite small and simple.

125 points by NSMeta 13y ago

gchaix 13y ago

Who put containers in my Vagrant!?

deleted 13y ago
[deleted]

polvi 13y ago

Alex from CoreOS here: This only supports virtualbox at the moment, but we are actively working on adding VMware. Fill out the form on this page if you want us to spam you when we have the vmware image (or others): http://coreos.com/ http://coreos.com/

OafTobark 13y ago
Any plans for Parallels?
- polvi 13y ago
  Not at the moment. That said, we will be publishing raw images that should be portable to just about anything.
- turboroot 13y ago
  Vagrant supports VMWare, but not Parallels yet.
  - akulbe 13y ago
    Oh? I just tried to get one with the instructions on their github page, and it said the box type was vbox. Are the vmware versions kept elsewhere?
    - hoverbear 13y ago
      He was talking about Vagrant (the tool CoreOS uses to distribute VM images)... Also, I think you can just make a directory in the `~/vagrant.d/boxes/coreos` folder called "vmware" and copy over the vagrant file, box.ovf and the metadata.json. Then you just edit the metadata to have a vmware provider and the box.ovf to reference "../virtualbox/<<theimage>>" I however do not have a vagrant vmware license and cannot test this theory.
    - akulbe 13y ago
      Wow. I got voted down for this? You guys are great. :/
runarb 13y ago
Why no VMware, Xen or Qemu? We can help you if you have any issues with making thus work you know :)

makerops 13y ago

You guys really should change the logo to a cookie, every time I see the url I think of oreos.

2mur 13y ago
I was thinking it should be a chewed on apple core, but now I cannot unsee the oreos... so I vote cookie logo too! Cool project
- Aldo_MX 13y ago
  How about a chewed oreo?

WestCoastJustin 13y ago

To anyone wanting to learn more about Vagrant via a screencast, I've created one @ http://sysadmincasts.com/episodes/4-vagrant http://sysadmincasts.com/episodes/4-vagrant

ChikkaChiChi 13y ago

Vagrant for the uninformed: Headless interface to VirtualBox and VMWare VMs on OSX. Instancing is made a breeze.

liamk 13y ago
ChikkaChiChi, that may be the single best explanation for what Vagrant is. Most people answer: "It provisions VMs" which isn't as enlightening as your answer!
DigitalJack 13y ago
It isn't specific to osx is it?
- jtreminio 13y ago
  It is not! Works on Linux, Mac and Windows.
radioact1ve 13y ago
Very good and simple explanation though I'd add Linux and Windows in there too.

passfree 13y ago

This is not related to the Vagrant<->CoreOS topic but since Vagrant box image format is a packaged ovf image it shouldn't be too hard to port the CoreOS images to Vortex (https://github.com/websecurify/node-vortex https://github.com/websecurify/node-vortex).

damm 13y ago

Ahh another Gentoo distro. Never ceases to amaze me how people troll it and yet it keeps popping out in every nook and cranny. https://github.com/coreos/coreos-overlay/ https://github.com/coreos/coreos-overlay/ Must have been a good idea that no one got.

wmf 13y ago
AFAIK CoreOS is based on ChromeOS which uses some parts from Gentoo. That doesn't mean Gentoo was ever a good idea for general-purpose PCs or servers.
- damm 13y ago
  Nice burn on Gentoo. I've had the job of supporting Gentoo on a PaaS and have deployed it many places happily. Sadly one of the dumbest arguments ever that will blacken the Linux horizon for decades, big dick syndrome over what Linux distro you run.
  - vertex-four 13y ago
    Where can I find the page which guarantees me that any given version of any given package will be fully supported by a defined security team for security fixes for at least 2 years from release, preferably 3+? That is my argument against using Gentoo. I have absolutely no idea how long any given piece of it will be supported. If you can point me to a resource which explains that, I might take another look. I also have no interest in picking and choosing packages out of a bucket - I want a stable, well-defined OS that I can build on, and preferably one which is as close to what everyone else is using as possible so I can ask for help from people who understand my OS. Yes, it might work out if you're running at scale, have specialised needs, and can dedicate resources to what essentially amounts to development of a forked distro. It doesn't work out for me, as I need to know that the system I'm building isn't going to be unsupported in a couple of months, and I need to know I can talk to someone who is running similar versions of everything I'm running if everything goes wrong.
    - 13y ago

hosay123 13y ago

I don't want to sound overly negative, but attempting to support every useful combination of hardware and drivers, particularly in any kind of supported, certified configuration, ultimately leads back to the same result: just running a real OS. You can look at CoreOS the same way as the Xen hypervisor and VMWare ESX: the more flexible these became (new hardware drivers, supported configurations, etc. etc) the more they began to look like general purpose operating systems. At which point, why not start with one? (Kvm followed the same logic) I'd much rather see the guts of CoreOS available as e.g. a RHEL or Debian package. As it stands, throwing away 20 years of distribution experience just to avoid installing a few files on my server seems far from worth it.

devinus 13y ago
You just described the actual draw of CoreOS. CoreOS is just Linux. Instead of going the Xen route you just described, it can capitalize on being just Linux by supporting everything Linux already supports. At this point, you can view CoreOS, which is just Linux, as the "hypervisor." Containers don't have to replicate key subsystems in every paravirtualized instance, as containers share all the same subsystems like e.g. the TCP/IP stack. You're also not throwing away any distribution experience. Want CentOS? Create a CentOS container with Docker. Want Ubuntu? Create an Ubuntu container with Docker. These are incredibly powerful ideas I'm just now being exposed to.
- hosay123 13y ago
  Try telling your SAN vendor that you're running "just Linux" and can you have a driver and support package for that please, and let us know how you get on. When you're done there, now try plugging your nice new machine into the corporate DC. Oh it seems it needs to support VLAN tagging. No problem, better just write some new code for that. Time to migrate a bunch of performance sensitive services. Uh oh, no support for FusionIO PCI SSDs! Better write some more code. Time to migrate your remote sites, only policy dictates certain services must be physically encrypted. No problem, better just cutpaste Debian's cryptsetup scripts and be done with it. Oops, turns out we deployed 1000 machines with a duff BIOS setting. No problem, I'm sure the server vendor has a support package for CoreOS.. We could come up with examples until we've basically reinvented a modern Redhat/Debian initramdisk and boot environment.

amalag 13y ago

Simple question, but if there is no package management, how do you install basic programs? Download binaries for everything?

ceejayoz 13y ago
I believe it's intended to be a minimal OS for running containers like those made by Docker (http://www.docker.io/ http://www.docker.io/).
devinus 13y ago
Simple answer: you don't. Longer answer: It depends. Do you want to use yum or apt-get to install programs? If you like CentOS, create a CentOS container with Docker and begin installing programs using yum! Ubuntu? Spool up an Ubuntu container and apt-get away! CoreOS is just the cradle upon which you can run the userland of any distribution you please.
- amalag 13y ago
  So CoreOS is the simple host OS, thank you for the clarification, i thought it was a minimal guest OS.

hcarvalhoalves 13y ago

What's the idea behind CoreOS? I found the site incredibly weak in information about what it is.

devinus 13y ago
I've just begun looking into and playing with CoreOS. Basically, it's a minimal Linux image with Docker, service discovery using the `etcd` daemon they've written in Go, and several interesting properties. The most interesting is their use of the ChromiumOS build tools, allowing them to one day update servers the same way e.g. ChromeOS is updated--using the Omaha protocol to push raw binary diffs of the new root FS.

tbe 13y ago

This reminds me of Bedrock Linux, which allows you to run multiple linux distros on a single kernel instance. It does so using good old chroot, but has an implementation that is capable of breaking out of the chroot when entering a new one. This way the different environments become more integrated in that a RHEL binary can call a Debian binary and so on, creating a sort of super distro which is itself quite small and simple.