Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker Raises $23M

docker.com

Post reply on HN
Print view View original

201–210 of 281 posts

Re: Docker Raises $23M

#201

Post by zapita »

mroche wrote: post #144
zapita wrote: post #36

Earlier quoted context omitted.

K8S uses containerd which is the official Docker runtime.

The difference being that Google has deprecated the shimming to Docker they had been doing with the “Docker” runtime to access containerd, so now it will go straight to the source by default. Red Hat OpenShift also switched from using Docker as its runtime with OpenShift 4 in 2019, though it was in favor of CRI-O rather than containerd.

All accurate. My point is that Kub deprecating the shimming does not affect Docker’s popularly or market share either way. The existence of the shim was an implementation detail and Docker themselves have been encouraging the switch to containerd. They clearly want the Docker brand to be attached to developer-facing tools instead of a hidden piece of increasingly commoditized infrastructure.

If a critical mass of kubernetes deployments switched from containerd to cri-o, that would be more problematic for Docker, but that seems unlikely to happen. Openshift to my knowledge is the only major kubernetes distribution not based on containerd. At this stage of the adoption cycle, cri-o is unlikely to be more than a distant second to containerd.

Re: Docker Raises $23M

#202

Post by mleonhard »

I've been waiting for two features from Docker:

1. Launch a container by specifying its image digest, not image ID [0] [1]. You can pull an image with a specific digest, but then it gets an ID that is unique to the image repository. Later deployments must use that different image ID. This makes deployment tooling needlessly complicated. And it breaks the security guarantees of the digest by allowing the repository to modify the image.

2. Copy a file into a container with docker-compose, without requiring Swarm [1].

Do financial problems explain their slowness? I wish they would just charge $100/year per seat for Docker for macOS and then fix the long-standing problems.

And sell a hosted tool to do trusted builds of docker images from hashed sources. Reproducible builds would be great, too.

[0] https://github.com/moby/moby/issues/16482#issuecomment-29782...

[1] https://windsock.io/explaining-docker-image-ids/#contentaddr...

[2] https://github.com/docker/compose/issues/5523

Re: Docker Raises $23M

#203

Post by random5634 »

ncallaway wrote: post #87
random5634 wrote: post #77

Earlier quoted context omitted.

Heads up - most users do NOT care about tracking, and click yes to these popups. Do folks on HN not get this? This is all posturing. If you want to reduce tracking, use a browser that reduces the tracking. Seriously, just use total cookie protection or something on firefox.

> most users do NOT care about tracking, and click yes to these popups By a corollary, some users DO care about tracking and click "no" to these popups.

Which ends up doing almost nothing in terms of actual tracking.

Re: Docker Raises $23M

#205

Post by tpetry »

mleonhard wrote: post #202

I've been waiting for two features from Docker: 1. Launch a container by specifying its image digest, not image ID [0] [1]. You can pull an image with a specific digest, but then it gets an ID that is unique to the image repository. Later deployments must use that different image ID. This makes deployment tooling needlessly complicated. And it breaks the security guarantees of the digest by allowing the repository to…

I would pay 100$/month if they would solve the slow filesystem performance. Every workaround solution has some problems, most often high latency or simply stopping the sync.

Re: Docker Raises $23M

#206

Post by ncrmro »

goatinaboat wrote: post #193
halfmatthalfcat wrote: post #176

Earlier quoted context omitted.

I beg to differ. The jump from learning Docker (and containers generally) to learning Kubernetes is not “hard”. Sure it’s a different paradigm of application deployment but I’ve seen far too many posts on HN that completely undermine its value in the name of difficulty. You can use it if you’re not “at scale” completely fine and reap all the benefits as if you were. Idk it’s because people hate Google, so they hate K…

I beg to differ. The jump from learning Docker (and containers generally) to learning Kubernetes is not “hard”. Unless you are at a scale that you can employ a full-time Kubernetes team, you probably don't need Kubernetes, and if you insist on using it for production anyway, you absolutely should use one of the many managed offerings (DO is probably cheapest, I have no affiliation with them), or shrinkwrapped product…

Actually with k3s it’s pretty dang simple!

Re: Docker Raises $23M

#207

Post by sneak »

filleokus wrote: post #76

It feels like Docker (Inc) is becoming less and less "relevant" for each year that passes. At least from my perspective, they led the popularisation of containerisation and the whole cattle-not-pets approach of deploying apps. They created big and long lasting change in the industry. But they seem to have lost the production environment race to Kubernetes, at least for now. They are the biggest player in the dev-mach…

> It feels like Docker (Inc) is becoming less and less "relevant" for each year that passes.

This is underscored for me by the fact that their latest end-user (dev) tools aren't even free software any longer. They started off being unixy as hell, doing one thing and doing it well (and being hackable in the process), and now they ship closed-source spyware under the exact same brand.

Re: Docker Raises $23M

#208

Post by gravypod »

411111111111111 wrote: post #189
halfmatthalfcat wrote: post #176

Earlier quoted context omitted.

I beg to differ. The jump from learning Docker (and containers generally) to learning Kubernetes is not “hard”. Sure it’s a different paradigm of application deployment but I’ve seen far too many posts on HN that completely undermine its value in the name of difficulty. You can use it if you’re not “at scale” completely fine and reap all the benefits as if you were. Idk it’s because people hate Google, so they hate K…

Using k8s to deploy is easy, setting up a cluster with the 'new' admin command is also straightforward... Doing maintenance on the cluster isn't. Debugging routing issues with it isn't either, configuring a production worthy routing to begin with isn't easy either. it's only quick if you deploy weave-net and call it a day. I would strongly discourage anyone using k8s in production unless it's hosted or you have a ful…

Very few people who suggest using kubernetes are suggesting using kubespray or kubeadm. 99% of companies will want to just pay for a managed kubernetes cluster which, for all intents and purposes, is basically AWS ECS with more features and less vendor lockin.

It should be also known that all "run your code on machines" platforms (like ECS) have similar issues. I remember using ECS pre-fargate and dealing with a lot of hardware issues with the instance types we were on. It was a huge time sink.

> it's only quick if you deploy weave-net and call it a day

That's exactly the benifit of kube. If something is a pain you can walk up to one of the big players and get an off-the-shelf solution that works and spend very little time integrating it into your deployment. No cloudformation stacks or other mess. Just send me some yaml and tell me some annotations to set on my existing deployments.

> I would strongly discourage anyone using k8s in production unless it's hosted or you have a full team whose only responsibility is it's maintenance, provisioning and configuration

If you have compute requirements at the scale where it makes sense for you to manage bare metal it should be pretty easy for you to find budget for 2 to 5 people to manage your fleet across all regions.

Re: Docker Raises $23M

#209

Post by initplus »

mav3rick wrote: post #168
bityard wrote: post #152

Earlier quoted context omitted.

Well, Docker is a Linux technology. If you really need Docker that badly and can't take the overhead of a VM, then it sounds like you would be better off just running Linux like the rest of us. :)

There is a container runtime / API to abstract this. Pretty sure Windows has equivalents of namespaces and cgroups.

The docker tools themselves ARE cross platform, but 99% of docker images in the wild are based off Linux, and have ELF binaries inside. Windows does not have equivalents for every single Linux system call. This is why you need WSL.

You can build an image based on a Windows base image, and run it natively in Windows.

Re: Docker Raises $23M

#210

Post by pjmlp »

IgorPartola wrote: post #192
pjmlp wrote: post #111

Earlier quoted context omitted.

I was already doing containers with HP-UX Vaults in version 11 back in 1999. Just like any tool that doesn't offer more than an abstraction layer over OS features, eventually it becomes irrelevant as OS tooling improves.

Portability is key. Being able to run an Ubuntu container on macOS is a killer feature.

Containers aren't virtual machines.
Post reply on HN