Closed keithy closed 4 years ago
This seems interesting, but conflicts with the current implementation.
Perhaps adding a new dockerfile/image for this purpose might be cleaner.
Fedora Atomic Host as an OS is almost officially End of Life, since it has been superceeded by Fedora Core OS. The "atomic" tool and this way of providing super-priviledged containers is no longer relevant.
oh.. hah. This is part of the reason why goss has almost no container support aside from wrapper scripts (e.g. dgoss).. I figure the ecosystem will be changing a lot until the industry normalizes on a set of tools.
Thanks for the initial PR. If there are any other use-cases for goss that you have, please let me know.
Oh, one last thing.. is there a new "super container" concept? I did not experiment with Fedora Core OS or Fedora silverblue yet to know what's the latest experimental work on that front.
This is being discussed: https://github.com/coreos/fedora-coreos-tracker/issues/37 I made some progress: https://github.com/coreos/fedora-coreos-tracker/issues/311
The options for FCOS basically are: A) Upload a binary directly (or publish an rpm to be overlayed) to the main OS.
This tool (when complete) https://github.com/keithy/ign-tool can be used to assemble an ignition provisioning script. This tool includes the ability to include modules or "plugs" as I call them. The "Plugs" are published via the github wiki and this solution should converge over the next few days!
The two options are,
1) a systemd portable service that runs goss serve
on a port (continuously/on demand)
b) a user that is allocated a safe-chrooted-shell (also provided via systemd)
Since all the niceness is provided by systemd, this solution ought to work similarly on other systemd based distributions.
This is extremely informative, thanks. Interesting to see all the new container centric distributions.
https://github.com/keithy/atomic-host-goss
This functionality works standalone, but could be merged into the mainline release.
atomic
tool.