Taking Another Crack at Installing CoreOS

44 views
Skip to first unread message

jm

unread,
Aug 13, 2018, 4:06:04 AM8/13/18
to coreo...@googlegroups.com

I have a few days spare this week between tasks and though I'd have
another go at installing CoreOS. This time on three spare laptops I have
in the office to form a cluster. So far I create a simple cloud-init and
feed it to ct to generate the ignition.json file. I then boot CoreOS on
one of the laptops via an ISO image on a USB stick and pull the
ignition.json file with curl and run

   coreos-install -i ignition.json -d /dev/sda

 after it boots into the installed CoreOS it automatically updates the
image and reboots. This is using the public etcd service. I have my ssh
key configured and can log in remotely.

The bit I'd getting stuck on is the next step. Getting Docker, and
everything else installed and configured. It appear the method of doing
this has changed leaving documentation is out of date or stopping just
as about where an example cloud-config should be given. For starters I'm
not even sure what is needed besides Docker. Does anyone have an example
cloud-init file for a simple three machine cluster with all three
machines running etcd, Docker, and whatever else is needed?


Regards,

Jeff.


Seán C. McCord

unread,
Aug 13, 2018, 8:59:23 AM8/13/18
to jm, coreo...@googlegroups.com
An excellent place to look for some scenario-based example configurations is in the matchbox examples directory[1].  You won't find Docker being _installed_ there, because Docker is already installed in CoreOS Container Linux.  What you will find is examples of various container-based applications as systemd units, which, if you are not using kubernetes, is the preferred way to run software.



--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Seán C McCord
CyCore Systems, Inc
Reply all
Reply to author
Forward
0 new messages