Tomster/Fedora-CoreOS-Ignition
1
0
Fork 0
mirror of https://github.com/tommytran732/Fedora-CoreOS-Ignition synced 2024-11-22 01:11:34 -05:00
Code
Ignition configurations for Fedora CoreOS
113 Commits 1 Branch 0 Tags 1.6 MiB
0090193dfc
Go to file
Tommy 0090193dfc
Remove non-functional /etc/issue 
Signed-off-by: Tommy <contact@tommytran.io>
2023-12-18 13:44:17 -07:00
Mailcow Add files via upload 2021-11-02 22:32:22 -04:00
.gitignore Use SSHD socket 2022-12-26 10:17:18 -05:00
Docker-Compose.ign Remove non-functional /etc/issue 2023-12-18 13:44:17 -07:00
Docker-Compose.yml Remove non-functional /etc/issue 2023-12-18 13:44:17 -07:00
Fedora-CoreOS-Ignition.code-workspace Add workspace config 2023-06-08 14:26:54 -07:00
Generic.ign Remove non-functional /etc/issue 2023-12-18 13:44:17 -07:00
Generic.yml Remove non-functional /etc/issue 2023-12-18 13:44:17 -07:00
kargs Add license notice 2023-12-06 22:46:17 -07:00
LICENSE Update LICENSE 2021-11-02 22:33:23 -04:00
README.md Update README.md 2023-10-11 23:19:54 -07:00
UTM.ign Remove non-functional /etc/issue 2023-12-18 13:44:17 -07:00
UTM.yml Remove non-functional /etc/issue 2023-12-18 13:44:17 -07:00

README.md

Fedora-CoreOS-Ignition

Ignition configurations for Fedora CoreOS

Notes

  1. These are the configs I personally use on my systems. You MUST edit the files before you use them. At the very least, you should add your SSH keys or password hash.
  2. Only ED25519 SSH keys are accepted with the SSHD hardening configuration. If you do not use ED25519 keys, you will need to edit the ExecStart=/usr/bin/curl https://raw.githubusercontent.com/TommyTran732/Linux-Setup-Scripts/main/etc/ssh/sshd_config/10-custom.conf -o /etc/ssh/sshd_config.d/10-custom.conf accordingly.
  3. If you create a passwordless user that requires administrative privileges, ensure that it is part of the sudo group (CoreOS allows this group to use sudo without a password) as the configs will disable empty password system authentication.
  4. These configurations are made with a VPS in mind. You should adapt it for a bare metal deployment if that is what you are using (adding additional kernel parameters, configuring drive encryption, configuring storage, etc). You should also change the tuned profile from virtual-guest appropriately.
  5. In most of these configs, the timezone is set to America/New_York and the automatic reboot time is set at 12 AM on Sunday. Watchtower will kick in 5-10 minutes after the reboot to update and redeploy the containers. You should change it according to your needs. The Docker-Compose.yml file does not include Watchtower.
  6. The auto-updater.service could be put in /etc/systemd/system and enable to have automatic updates for your docker-compose and its containers. Please make sure that the WorkingDir is appropriate.