9 Matching Annotations
  1. Jan 2026
    1. What has Docker become?
      • Docker Inc. has faced multiple identity crises since revolutionizing containerization, struggling to monetize its commoditized open-source core technology.
      • Pivoted from orchestration (sold Swarm after Kubernetes dominance) to developer tools like Docker Scout (supply chain security via Atomist acquisition) and Testcontainers (integration testing).
      • Shifted to AI with Model Runner, Compose for agents, Offload for GPUs, partnerships (Google Cloud, Azure), and MCP Defender acquisition for AI security.
      • Released 1,000+ free Apache 2.0 Hardened Images (95% fewer vulnerabilities) in response to Chainguard, questioning future revenue from security features.
      • CEO change to ex-Oracle exec sparks acquisition speculation by cloud giants; technology endures as infrastructure despite company uncertainty.

      Hacker News Discussion

      • Docker commoditized itself via open source; hard to monetize core tech, leading to pivots—enterprise ignored rootless/cgroups needs early, enabling Podman/Quay rise.
      • Criticism of Docker Desktop licensing "gotcha" tactics pushing users to Rancher/Colima/OrbStack; developer tools market tough as devs resist paying.
      • Defenses: maintained OCI runtimes (runc/containerd origins), free hardened images generous; AI/exploration necessary amid hyperscaler dominance.
      • Swarm never meant to rival K8s; Podman docs lacking, but rootless superior; alternatives like gVisor, Apple container, Nix praised.
      • Broader: open infra hard to profit (e.g., Redis forks); VCs expect quick exits; Docker success lives on despite company struggles.
  2. May 2024
    1. Podman commands are the same as Docker’s When building Podman, the goal was to make sure that Docker users could easily adapt. So all the commands you are familiar with also exist with Podman. In fact, the claim is made that if you have existing scripts that run Docker you can create a docker alias for podman and all your scripts should work (alias docker=podman). Try it.
  3. Mar 2022
    1. Have you ever built an image only to realize that you actually need it on a user account other than root, requiring you to rebuild the image again in rootless mode? Or have you built an image on one machine but run containers on the image using multiple different machines? Now you need to set up an account on a registry, push the image to the registry, Secure Shell (SSH) to each device you want to run the image on, and then pull the image. The podman image scp command solves both of these annoying scenarios as quickly as they occur.

      Podman 4.0 can transfer container images without a registry.

      For example: * You can copy a root image to a non-root account:

      $ podman image scp root@localhost::IMAGE USER@localhost:: * Or copy an image from one machine to another with this command:

      $ podman image scp me@192.168.68.122::IMAGE you@192.168.68.128::

  4. Sep 2021