summaryrefslogtreecommitdiff
path: root/_posts/2017-05-16-coreos-installation-on-a-hetzner-server.md
blob: f84a9435f3face797c19208259599d28b33f007b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
---
layout: post
title: "CoreOS Installation on a Hetzner Server"
description: ""
category: 
tags: []
---
{% include JB/setup %}

- log into the rescue system

    `ssh root@{sever-ip}`

- run `installimage`

  - choose "Other" -> "CoreOS-XXX"
  - keep the default install.conf (you may have to quit with ESC 0, if F10 does not work)
  - confirm deletion of partitions

* reboot into CoreOS

    `reboot`

- log into CoreOS (using the same password as for the rescue system)

    `ssh root@{sever-ip}`

CoreOS overwrites user data in /etc during booting (e.g. after a automatic system update). In order to make persistent changes, we have to edit
`/var/lib/coreos-install/user_data`:

    - set the hostname
    - add your public SSH key for the core user
    - disable sftp `#Subsystem sftp internal-sftp`
    - disable root login `PermitRootLogin no`
    - disable password authentication `PasswordAuthentication no`

The docker systemd service is not enabled by default, but we need it to restart docker services after a reboot:

    `systemctl enable docker.service`

Reboot to test changes:

    `reboot`

Make sure you can login as core user:

    `ssh core@{sever-ip}`