5 ms·

I heard you like abstract tools to do stuff, so I added an abstract tool to your tool to manage abstract tooling.

thayne 4y ago
https://en.m.wikipedia.org/wiki/Fundamental_theorem_of_software_engineering https://en.m.wikipedia.org/wiki/Fundamental_theorem_of_softw...
dilyevsky 4y ago
If it still cant send and read email there’s room for improvement
- crest 4y ago
  [flagged]
  - bronson 4y ago
    Do you know of a fix for offtopic snark?
pxc 4y ago
This is actually a pretty natural fit, imo. Docker containers are basically processes with fat runtimes, and container orchestration layers are essentially glorified process supervisors. At the same time, most Linux systems already come with a pretty fancy process supervisor. Personally, I think writing systemd units from scratch is already pretty easy. But it makes sense that Linux software which often integrates with (essentially) process supervisors would want painless integration with systemd! Also, in some ways I think this is simpler. Anyone who has used a reasonably modern Linux likely has some systemd experience. For local testing and 'orchestration', why rely on some additional one-off layer like docker-compose when the operating system's built-in process supervisor has all of the facilities you need?
- groestl 4y ago
  > container orchestration layers are essentially glorified process supervisors. There is a little more to container orchestration runtimes. Would say at this time they are akin to a badly designed, distributed linker (I'm saying this as someone who did not fully buy into this stuff, but I see that it solves some problems)
- imiric 4y ago
  > Also, in some ways I think this is simpler. Not really. Being simpler would be managing containers directly with systemd, as with systemd-nspawn. Why do I need to use a container manager in systemd for something systemd can already do directly? This integration with Podman is Red Hat's way of promoting the tool to stay relevant, but it's not actually simpler.
  - guipsp 4y ago
    nspawn cannot download or update containers for one
quickthrower2 4y ago
Terraform run from CI pipeline enters the chat

https://en.m.wikipedia.org/wiki/Fundamental_theorem_of_software_engineering https://en.m.wikipedia.org/wiki/Fundamental_theorem_of_softw...

dilyevsky 4y ago

If it still cant send and read email there’s room for improvement

crest 4y ago
[flagged]
- bronson 4y ago
  Do you know of a fix for offtopic snark?

pxc 4y ago

This is actually a pretty natural fit, imo. Docker containers are basically processes with fat runtimes, and container orchestration layers are essentially glorified process supervisors. At the same time, most Linux systems already come with a pretty fancy process supervisor. Personally, I think writing systemd units from scratch is already pretty easy. But it makes sense that Linux software which often integrates with (essentially) process supervisors would want painless integration with systemd! Also, in some ways I think this is simpler. Anyone who has used a reasonably modern Linux likely has some systemd experience. For local testing and 'orchestration', why rely on some additional one-off layer like docker-compose when the operating system's built-in process supervisor has all of the facilities you need?

groestl 4y ago
> container orchestration layers are essentially glorified process supervisors. There is a little more to container orchestration runtimes. Would say at this time they are akin to a badly designed, distributed linker (I'm saying this as someone who did not fully buy into this stuff, but I see that it solves some problems)
imiric 4y ago
> Also, in some ways I think this is simpler. Not really. Being simpler would be managing containers directly with systemd, as with systemd-nspawn. Why do I need to use a container manager in systemd for something systemd can already do directly? This integration with Podman is Red Hat's way of promoting the tool to stay relevant, but it's not actually simpler.
- guipsp 4y ago
  nspawn cannot download or update containers for one

quickthrower2 4y ago

Terraform run from CI pipeline enters the chat