Work in progress: 82,651 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #1314

D

Dagger

Company blog · dagger.io/blog · on HN as shykesprogrammingsystems

Dagger is the company blog at dagger.io, writing about programming and systems. Since 2021, 53 different Hacker News readers have linked it 125 times, most often “Dagger: Define software delivery workflows and dev environments”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
125mentions?
53HN people?
2021–2026first – last linked?
Links on Hacker News per year · peak 32 in 2025

Dagger is third-generation CI, after Jenkins and GitHub Actions. It is built to match the speed and scale of coding agents and give them the guardrails and context they need.

The author on HN?

shykes · 7,921 karma · member since 2008

http://dagger.io Solomon Hykes. Co-founder of Docker (YCS10) and Dagger (YCW19). @solomonstre @dagger_io http://www.linkedin.com/in/solomonhykes http://www.github.com/shykes

From their public HN profile, which links to this site.

Most-linked posts?

  1. Dagger: Define software delivery workflows and dev environments
    25 people · 30 mentions · first linked 2021-10-17
  2. /
    12 people · 30 mentions · first linked 2021-08-19
  3. Ending Support for the Dagger Cue SDK
    3 people · 4 mentions · first linked 2023-12-18
  4. Dagger 1.0 Beta
    2 people · 3 mentions · first linked 2026-10-23
  5. The great CI bottleneck of 2026
    2 people · 3 mentions · first linked 2026-09-21
  6. How we Release Dagger
    2 people · 2 mentions · first linked 2023-03-22
  7. Dagger NodeJS SDK: Develop Your CI/CD Pipelines as Code
    2 people · 2 mentions · first linked 2022-11-17
  8. Dagger: A shell for the container age
    2 people · 2 mentions · first linked 2025-03-26
  9. Dagger Functions
    2 people · 2 mentions · first linked 2024-02-29
  10. CI pipelines should be code: introducing the Dagger Go SDK
    2 people · 2 mentions · first linked 2022-10-25

What Hacker News says?

  1. By the way, I just launched my new thing today :) They say lightning never strikes twice, but you never know! I hope the plug is appropriate in this setting - apologies if not. https://dagger.io/blog/dagger-10-beta/

    Comment linking /blog/dagger-10-beta/

    on “Docker is weird”
  2. Submitted Dagger: a new way to build CI/CD pipelines as a story · 397 points

    HN discussion
  3. I did make a bunch of money with Docker, something I am eternally grateful for. I did not start a band, but I did build a nice house, help my family etc. I still program everyday, working on my second startup, https://dagger.io (please forgive the plug). We have a very active discord if you want to come say hi.

    Comment linking /

    on “Docker is weird”
  4. Submitted We replaced our React front end with Go and WebAssembly as a story · 250 points

    HN discussion
  5. I'll be digging deeper on these ideas on a webinar on the 15th if this topic is interesting to you! https://dagger.io/webinar/agentic-ci

    Comment linking /webinar/agentic-ci

    on “Writing Code Was Never the Bottleneck”
  6. Submitted Dagger: A shell for the container age as a story · 199 points

    HN discussion
  7. > GHA has "service containers", but unfortunately the feature is too basic to address real-world use cases: it assumes a container image can just … boot! … and only talk to the code via the network. Real world use cases often require serialized steps between the test & the dependencies, e.g., to create or init database dirs, set up certs, etc.) My biased recommendation is to write a custom Dagger function, and run i…

    Comment linking /

    on “Testcontainers”
  8. Submitted Dagger Python SDK: Develop Your CI/CD Pipelines as Code as a story · 161 points

    HN discussion
  9. Dagger ( https://dagger.io ) recently seems to have reinvented/rebranded itself as some llm agent platform.

    Comment linking /

    on “The Pain That Is GitHub Actions”
  10. Submitted Dagger: Define software delivery workflows and dev environments as a story · 77 points

    HN discussion
  11. Dagger does what you're describing: https://dagger.io/

    Comment linking /

    on “GitHub Actions has a package manager, and it might be the worst”
  12. Submitted Dagger.io – A Portable Devkit for CI/CD Pipelines as a story · 35 points

    HN discussion
  13. I support the effort to build a platform-agnostic CI/CD pipeline solution, but I don't want it in the form of yet another platform. Rather it needs to be a protocol that any platform can tie in to. I'm especially wary since this is another VC-backed effort that will eventually need to be monetized in some shape or form. Additionally, as someone else here has already mentioned, my mind first went to Dagger, the depen…

    Comment linking /trademark

    on “Dagger: a new way to build CI/CD pipelines”
  14. Submitted Dagger Functions as a story · 24 points

    HN discussion
  15. Sounds a lot like https://dagger.io/ . Maybe you can take some inspiration from them

    Comment linking /

    on “Ask HN: What are you working on (September 2024)?”
  16. Submitted Dagger 1.0 Beta as a story · 17 points

    HN discussion
  17. See https://dagger.io , the next gen tool by the creators of docker that does this. CUE + BuildKit

    Comment linking /

    on “Will Nix Overtake Docker?”
  18. Submitted CI pipelines should be code: introducing the Dagger Go SDK as a story · 14 points

    HN discussion
  19. I call this moment "the Great CI Bottleneck of 2026". Here are my thoughts on it: https://dagger.io/blog/the-great-ci-bottleneck-of-2026/

    Comment linking /blog/the-great-ci-bottleneck-of-2026/

    on “AI coding has made CI a bottleneck, so we reworked ours to keep up”
  20. Submitted Dagger NodeJS SDK: Develop Your CI/CD Pipelines as Code as a story · 10 points

    HN discussion
  21. Yes, I use Dagger, it's much more than building containers - Container based workflows are the same in CI and locally (you can run containers too), they become one-liners - Remote caching out of the box without extra steps - Multiple language SDKs, unlocks the DAG in BuildKit and containers, real reuse - Obfuscates secrets from your logs and agents. I've built an agent environment on Dagger, which also includes fork…

    Comment linking /changelog/theseus/

    on “Roku developer repositories moved from GitHub to GitLab”
  22. Submitted Dagger 0.14 as a story · 9 points

    HN discussion
  23. > These alternatives are far more familiar and easier to work with. You can get most (but not all) of the benefits of NixOS with far less work. > Worse is better. There are some potential alternatives out there that seem inspired by Nix but which are less strict. I think a system that offers and manages Nix's purity but doesn't require it could end up the final winner some day. Shea Levy had some ideas for eventuall…

    Comment linking /

    on “Our Roadmap for Nix”
  24. Submitted Introducing Dagger Functions as a story · 8 points

    HN discussion
  25. Because I'm typically building and running tests in containers in CI, which is what dagger is for. nu is my default shell. Note that I am not talking about dagger shell. https://dagger.io/blog/a-shell-for-the-container-age-introdu...

    Comment linking /blog/a-shell-for-the-container-age-introducing-dagger-shell

    on “Run GitHub Actions locally”
  26. Submitted LLMs as basic building blocks of software delivery as a story · 4 points

    HN discussion
  27. I'd encourage anyone thinking of using make to look at alternatives. Make is great, but is quickly becomes a ball of duct-tape. Make works very well when you spend the time to express your dependency tree, but realistically that never happens and people tend to add hacks upon hacks for Makefiles. Not only that, but they don't scale well as your project adds more components, such as integration testing, documentation…

    Comment linking /

    on “The Unreasonable Effectiveness of Makefiles”
  28. Submitted A Shell for the Container Age: Introducing Dagger Shell as a story · 4 points

    HN discussion
  29. For CI specifically, you should IMO check out https://dagger.io . It abstracts and generalizes CI in exactly the way you need: repeatable, locally runnable, and also cacheable on remote servers. Write once, run anywhere CI - what you have locally will be _exactly_ what runs remotely.

    Comment linking /

    on “Automating a Software Company with GitHub Actions”
  30. Submitted The Daggerverse as a story · 4 points

    HN discussion

Search all of HN for dagger.io

Linked by the same people?