python and semanage were removed from coreos recently.

[guest20]

Version:
This bug prevents installation so I can't run k3s -v, but the current tag is v1.0.0

Describe the bug
The install script bails out when looking for semanage:

core@localhost ~ $ curl -sfL https://get.k3s.io | sh - 
which: no semanage in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/opt/bin)
[ERROR]  SELinux is enabled but semanage is not found

To Reproduce

1. boot coreos: Container Linux by CoreOS stable (2247.7.0)
2. curl -sfL https://get.k3s.io | sh -

Expected behavior
A installed k3s

Actual behavior
Install fails with the message above.

Additional context
The discussion: coreos/fedora-coreos-tracker#126 - Keep/Remove Python dependent package: policycoreutils-python
The PR removing it: coreos/fedora-coreos-config#88

[MarkusTeufelberger]

CoreOS did never(?) have Python, your bug report links to Fedora CoreOS which is a different distribution.

[guest20]

@MarkusTeufelberger I don't know the history - it's possible that I've mis-diagnosed it and it never worked. All I know is that it doesn't work now.

[stellirin]

On CoreOS you shouldn't bother with install.sh, just set it in your ignition file directly, like:

https://github.com/stellirin/coreos-k3s-ceph/blob/master/ignition/k3s-server.yaml#L18
https://github.com/stellirin/coreos-k3s-ceph/blob/master/ignition/k3s-server.yaml#L114

[guest20]

thanks for the link @stellirin - I ended up doing something very similar in the end. This approach doesn't handle new releases very well though.

[westurner]

See: "Add support for SELinux" #1372

[brandond]

Also, CoreOS Container Linux is end-of-life; Red Hat is shunting everyone over to Fedora CoreOS, Flatcar, or RHEL CoreOS. I have no idea how any of them are related, but that probably explains why folks are referencing Fedora CoreOS issues.

https://coreos.com/os/eol/

[stale]

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.