I work in an ‘essential service’ environment for my main gig, where lots of checks and cross-checks need to exist. And it’s one that’s been under constant low-grade attack forever as it contains a LOT of tasty PII (personal info) and therefore has regs hammering it into shape. Docker cannot play here - and neither can Debian, actually, nor its derivatives - because it lacks the signed validation available in peer products sharing its space. As soon as the adults show up and notice a product with reduced validation is in place where a better one exists, the people owning that system have to write a life-cycle plan to upgrade, and it’s reviewed at an almost punitive frequency.
So, if you’re saying it’s a little too Corporate, I’m thinking you mean ‘suits and power lunches’ and not ‘large scale management of crucial systems and essential data’. True?
Tbh, I’ve never worked in such an environment. I know somebody who told me similar things and I would love to hear more about this to form my own opinion on this. But it’s just not that deep. When I say corporate, I mean it’s full of GUIDs and only machine-readable names, commands and configs. It’s also most of the time not designed with the flexibility in mind and covers only the most commonly (used by the company supporting it) use cases. It just doesn’t have the free spirit which most of the open source tools, which are designed with humans in mind, have. If you need to supply a parameter to get output from a command that is often run manually while you could also have one to deactivate output for script usage. This seems like the wrong way to go.
I work in an ‘essential service’ environment for my main gig, where lots of checks and cross-checks need to exist. And it’s one that’s been under constant low-grade attack forever as it contains a LOT of tasty PII (personal info) and therefore has regs hammering it into shape. Docker cannot play here - and neither can Debian, actually, nor its derivatives - because it lacks the signed validation available in peer products sharing its space. As soon as the adults show up and notice a product with reduced validation is in place where a better one exists, the people owning that system have to write a life-cycle plan to upgrade, and it’s reviewed at an almost punitive frequency.
So, if you’re saying it’s a little too Corporate, I’m thinking you mean ‘suits and power lunches’ and not ‘large scale management of crucial systems and essential data’. True?
Tbh, I’ve never worked in such an environment. I know somebody who told me similar things and I would love to hear more about this to form my own opinion on this. But it’s just not that deep. When I say corporate, I mean it’s full of GUIDs and only machine-readable names, commands and configs. It’s also most of the time not designed with the flexibility in mind and covers only the most commonly (used by the company supporting it) use cases. It just doesn’t have the free spirit which most of the open source tools, which are designed with humans in mind, have. If you need to supply a parameter to get output from a command that is often run manually while you could also have one to deactivate output for script usage. This seems like the wrong way to go.