Live data from Hacker News

Show HN: Container Desktop – Podman Desktop Companion

container-desktop.com

61–70 of 207 posts

Re: Show HN: Container Desktop – Podman Desktop Companion

#61
Orthogonal rant: Podman allows host mounts during image build, whereas docker does not. Ran into a big headache where a monorepo using podman leveraged this to create container images from source and the equivalent docker implementation had to copy the monorepo into the docker build context every time.

We needed to use Docker for M1 support (probably should've tried Colima, etc).

Re: Show HN: Container Desktop – Podman Desktop Companion

#62
post #61

Orthogonal rant: Podman allows host mounts during image build, whereas docker does not. Ran into a big headache where a monorepo using podman leveraged this to create container images from source and the equivalent docker implementation had to copy the monorepo into the docker build context every time. We needed to use Docker for M1 support (probably should've tried Colima, etc).

I may be wrong, but I think BuildKit gives Docker that functionality.

Re: Show HN: Container Desktop – Podman Desktop Companion

#63

Why does Docker feel like it was designed by people with no Unix background?

I don't know if your comment was intended to imply that Docker was against the Unix philosophy in some way (a debatable point, but not really one I share), or if you mean that the tools don't follow a lot of common Unix convension.

When Docker was only a few years old, I did keep running into lots of small things which implied that the people developing docker in fact did NOT have a Unix (or even Linux) background. Things like source code files having the wrong type of newlines (or a mix of types), and forgetting to add a newline to the last line in a file. (A correct Unix text file has a newline at the end of _every_ line, even the last one.) There were of course more giveaways than this, I just remember the newline stuff irritating me the most.

Re: Show HN: Container Desktop – Podman Desktop Companion

#64
post #45

Kubernetes is planned - my devops wants me to add it badly! Author note - Most of you guys here are power users, for whom UI is a visual poem that you need or not. This is not a commercial project, it is not following any business goals. But this does not mean concessions to quality, it does try to offer minimal resource usage everywhere, easy experience, good UI/UX. It explains all it does behind the scenes if you e…

I never finished it, but I had a lot of fun documenting a basic-ass K8S (well, K3S) setup that costs about 20€/mo on Hetzner.

You don't really learn about sysadmin through it, or even about docker that much, but you get an idea of how you might easily run a few different things on a server while only needing to know YAML, and not some custom DSL like chef or puppet.

Re: Show HN: Container Desktop – Podman Desktop Companion

#65
post #63

Why does Docker feel like it was designed by people with no Unix background?

I don't know if your comment was intended to imply that Docker was against the Unix philosophy in some way (a debatable point, but not really one I share), or if you mean that the tools don't follow a lot of common Unix convension. When Docker was only a few years old, I did keep running into lots of small things which implied that the people developing docker in fact did NOT have a Unix (or even Linux) background. T…

Why is newline at the end relevant?

I remember not having a newline breaks some tools... but why? It can't be because of unix philosophy!?

Re: Show HN: Container Desktop – Podman Desktop Companion

#66
post #45

Kubernetes is planned - my devops wants me to add it badly! Author note - Most of you guys here are power users, for whom UI is a visual poem that you need or not. This is not a commercial project, it is not following any business goals. But this does not mean concessions to quality, it does try to offer minimal resource usage everywhere, easy experience, good UI/UX. It explains all it does behind the scenes if you e…

[flagged]

Re: Show HN: Container Desktop – Podman Desktop Companion

#67
post #61

Orthogonal rant: Podman allows host mounts during image build, whereas docker does not. Ran into a big headache where a monorepo using podman leveraged this to create container images from source and the equivalent docker implementation had to copy the monorepo into the docker build context every time. We needed to use Docker for M1 support (probably should've tried Colima, etc).

I'd bind-mount the tree into the context. (I assume Docker won't follow simple symlinks.)

Re: Show HN: Container Desktop – Podman Desktop Companion

#68
post #13

Earlier quoted context omitted.

You should check out https://kind.sigs.k8s.io/ and https://k0sproject.io

I love kind! Used it a lot when I was writing my thesis on Kubernetes schedulers.

Literally or figuratively?

Re: Show HN: Container Desktop – Podman Desktop Companion

#69
post #61

Orthogonal rant: Podman allows host mounts during image build, whereas docker does not. Ran into a big headache where a monorepo using podman leveraged this to create container images from source and the equivalent docker implementation had to copy the monorepo into the docker build context every time. We needed to use Docker for M1 support (probably should've tried Colima, etc).

https://docs.docker.com/reference/dockerfile/#run---mount

Re: Show HN: Container Desktop – Podman Desktop Companion

#70
post #45

Kubernetes is planned - my devops wants me to add it badly! Author note - Most of you guys here are power users, for whom UI is a visual poem that you need or not. This is not a commercial project, it is not following any business goals. But this does not mean concessions to quality, it does try to offer minimal resource usage everywhere, easy experience, good UI/UX. It explains all it does behind the scenes if you e…

[flagged]

Like everything in tech, it's all about tradeoffs and understanding how you want to scale your business. Of the three startups I've been at, 2 of them adopted k8s early on and 1 of which didn't. Of the two that adopted k8s, one I would say k8s was our key differentiator in terms of our GTM motion and how our platform powered the business. $MM customer needs a setup running as close to their current infra's region for just about any reason, yeah sure we can spin that up in a week. This was often the key bit that allowed us to take customers from our key competitors before the competitor even knew we were in play. The 2nd one..... giant waste of money that gave me a decent pay check.

The third startup that opted _not_ to adopt k8s is stuck at $100M in revenue and can't land customers fast enough to offset churn. This is entirely because the COO has held the mentality "k8s bad, amirite?" and stuck with a patchwork of ansible scripts to manage configuring VM farms that ran our stack. Years of tech debt piled up and every new $MM customer coming in that needs to run in a specific region for $reasons, takes 6 months to setup and cost so much that we'd lose money on the deal. I genuinely believe this startup would be closer to $500M in revenue in the years since I've left had they invested in migrating from containers running in VM's to k8s. But instead they had to lay off 30% of their staff and get another round of funding, and are stagnating.

Post reply on HN