631–640 of 764 posts
Earlier quoted context omitted.
Is https://aws.amazon.com/ecr/ no good?
It's great. We migrated our images to it months ago (not because of this, bandwidth issues mainly, we also vendor our base images on it) and it has given us exactly 0 problems.
Earlier quoted context omitted.
To me is the opposite, Docker promotes bad software development practices that in the end will hurt you. In fact most of the time when you hear that you need Docker to run a software is because that software is so badly written that installing it on a system is too much complex. Another bad use of Docker that I've seen is because people cannot figure out how to write systemd units, that is damn simple (just spend a d…
I think you are letting your specific feelings and head-canon about purity be mistaken for solid technical arguments. If you’re sshing to boxes, editing things by hand and slinging ad-hoc commands around then your frame of reference is so far away from understanding it’s value proposition that it’s probably pointless to discuss it.
Earlier quoted context omitted.
It's great. We migrated our images to it months ago (not because of this, bandwidth issues mainly, we also vendor our base images on it) and it has given us exactly 0 problems.
This is what I don't understand about Docker's policy switch. Aren't all the companies that would potentially pay them just going to switch to one of the main CSPs Container Registry service?
Earlier quoted context omitted.
I think you are letting your specific feelings and head-canon about purity be mistaken for solid technical arguments. If you’re sshing to boxes, editing things by hand and slinging ad-hoc commands around then your frame of reference is so far away from understanding it’s value proposition that it’s probably pointless to discuss it.
Nix solves the ad-hoc problem much more cleanly than Dockerfiles do
I like nix - it’s probably the right direction, but just compare the UX to Docker. Comparatively Docker absolutely nailed it.
Earlier quoted context omitted.
> Is it though? Podman is more well liked (no daemon / non-root) and Kubernetes doesn't have direct support for it any more. I've used "Docker" as in "containerization", since they are often used synonymously and the grandparents intent was definitely to criticize the latter. Docker itself will quite likely stay around as a name, but I have no faith in the company.
It seems the company is slowly trying to make users pay for it. Not too long ago it was free for companies, then they made companies pay to use it. Now they're making people pay to store images. In the next few years I would be surprised if they didn't introduce a new way to monetize it, leading up to removing the use of any docker executable at all without payment. Many will come to comment "that's absurd, and you c…
Earlier quoted context omitted.
Nix solves the ad-hoc problem much more cleanly than Dockerfiles do
There’s purity of design/implementation and there’s usage. Often these are inversely related. I like nix - it’s probably the right direction, but just compare the UX to Docker. Comparatively Docker absolutely nailed it.
Just like Visual Basic 6, it's super-easy to get started with a Dockerfile, but nigh-on impossible to create a quality result with it.
Earlier quoted context omitted.
There’s purity of design/implementation and there’s usage. Often these are inversely related. I like nix - it’s probably the right direction, but just compare the UX to Docker. Comparatively Docker absolutely nailed it.
In many ways I agree with you. Just like Visual Basic 6, it's super-easy to get started with a Dockerfile, but nigh-on impossible to create a quality result with it.
Nix needs reproducible builds as well, which is a limiting factor. What’s nice about Docker is that it’s flexible enough to actually get stuff done.
Earlier quoted context omitted.
Docker should have been a neat tool made by one enthusiast, just like curl is. Instead it has a multi-million dollar company behind it, and VC's who demand profits from a thing that shouldn't have ever had a business plan.
Yeah! I should be able to get 50x value from software and not pay for it /s The open source community that carrier Docker on its back and is now bending over. Let this be a lesson to you. If you're building open source, maybe stick to open source solutions in your tech stack and if it's not there build it. This is what Apache does for the Java ecosystem. I don't have sympathy, the writing was on the wall and this isn…
You mean this Apache: https://github.com/apache ?
As an SRE Manager, this is causing me a hell of a headache this morning. In 30 days a bunch of images we depend on may just disappear. We mostly depend on images from relatively large organizations (`alpine`, `node`, `golang`, etc), so one would want to believe that we'll be fine - they're all either in the open source program or will pay. But I can't hang my hat on that. If those images disappear, we lose the abilit…
Many of the responses here are talking about how to vendor/cache images instead of depending on an online registry, but remember that you also need access to a supply chain for these images. Base images will continue to be patched/updated, and you need those to keep your own images up to date. Unless the suggestion is to build all images, from the bottom up, from scratch.
If docker pushes people to that, hopefully more reproducible solutions like nix and it's ux friendly "porcelains" such as https://devenv.sh/ gain market share.