• 1 Post
  • 136 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Well, that explains why corporate is so intent on them. They’re creating the perfect little KPI-driven stooge.

    Heck, now I’d like to see a study on KPIs (as a concept) as a reality distortion lens. It would seem like they have inadvertantly created a way to calculate a reality alignment index for a given KPI. Is it reasonable to conclude that using KPIs to measure performance is, in itself, unethical behavior?

    To go a bit further: Is there a correlation between the number of KPIs and the likelihood of creating scenarios in which the only desirable outcome lies outside reality? That is, how many KPIs does it take to get sufficient competition between priorities that it effectively requires hallucinating a solution to achieve a sufficiently aligned result?









  • Once podman is installed (iirc the network package is marked as a dependency for most package managers) and your user is configured (provide subuids/subguids), I really think podman is a simpler model. The containers you run are actually yours (not root’s) and you don’t need to be part of a privileged docker group to run them. Of course, you can run containers as root with podman too: just use sudo.

    You’ll actually need to configure your user the same way for running docker in rootless mode, which should be the default.

    Your dockerfile will work with podman. Your docker-compose file will too (via podman compose). You’ll have access to awesome new capabilities like pods, and defining your containers with kubernetes style yaml, and running your containers via systemd.

    However, with rootless podman/docker, you should remove any/all of the USER silliness the rootful/default docker people do to protect themselves a bit from rogue processes effectively running as root and/or container escapes to root.