3 ms·
I am so glad we don't play around in traffic with containerization bullshit. The opportunity for side channels is profound, the abstraction is leaky, and the am
by bob1029 6y ago
I am so glad we don't play around in traffic with containerization bullshit. The opportunity for side channels is profound, the abstraction is leaky, and the amount of engineering effort is non-trivial.
About 5 years ago we decided to take a path less-traveled with regard to applications development and deployment. We decided that our application is humble enough to run entirely on 1 powerful server. Sqlite is more than enough for our persistence needs. We don't need a huge orchestration of machines to get the job done. Instead, we decided to use self-contained deployments of .NET Core applications with all required dependencies embedded. This means we can email a zip file to a customer, they can extract it to any fresh windows/Linux vm, and then our code bootstraps the entire show.
All of our dependencies (the ones we are legally accountable for) are easily tracked in this approach. Introspection of msbuild dependencies is far easier than understanding the full extent of a docker image's vendor scope.
- deleted 6y ago[deleted]
- yjftsjthsd-h 6y ago> The opportunity for side channels is profound, the abstraction is leaky, and the amount of engineering effort is non-trivial. So you instead created, from scratch, a way to run all of your stuff directly on the host with absolutely no isolation? Indeed, you have eliminated side channels - by making them main channels!
- bob1029 6y ago> So you instead created, from scratch, a way to run all of your stuff directly on the host with absolutely no isolation? I like how we are able to frame basic application development like its somehow insecure by default and only with the blessing of containerization technology can it be made secure. If your application has serious side channel considerations, you should be running it on a dedicated host (with or without hypervisor/containers/et. al.). This is precisely what all of our clients do when hosting our application in their environments. Docker does not magically protect your application from others running on the same physical machine. The marketing materials may present it in this light, but there are foundational security considerations with running 2+ applications on the same physical CPU that go way deeper than OS-level containerization primitives.