Change:
url = "https://github.com/moby/moby/pull/43136.patch"; hash = "sha256-1WZfpVnnqFwLMYqaHLploOodls0gHF8OCp7MrM26iX8="; }) <ins> (fetchpatch { name = "fix-issue-with-go-1.20.6.patch"; url = "https://github.com/moby/moby/pull/45972.patch"; hash = "sha256-zxFh/bI6+INOYSg6QFs0S9rdl9Z21KUIZFmzpNVjpSA="; }) </ins> ]; postPatch = ''

Discussion:
docker fails to run containers since go has been updated to go1.20.6. Issue is known upstream: (concise explanation in ) Steps to reproduce the behavior: from the channel nixos-23.05-small a . Fails with I can run containers on my server :sob: While I'm waiting for a released fix on nixpkgs, how can I circumvent this? Easiest way seems to downgrade go version used to compile various docker binaries, but docker's can't accept overrides as various packages are built in a . Is there an easy way to revert commit in nixpkgs? Or is there any easy way to fix this? Thanks y'all! docker: go:
I find it very strange that I'm the first one reporting this issue, as has been merged on the 12th. Also I don't get why I already have it on my production system while !
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Same issue here, all my containers died on last auto upgrade.
You can also pin nixpkgs to a working commit. That is tracking the master -nixos-unstable path. The commit was backported to 23.05. It went through the staging branches first, that's why it took some time to show up in the stable branches. That's why it took so long to show up in production after the initial commit.
this to to to just before the : once. It updates the for future invocations. a second time. It rebuilds your system taking into account the new . Just hope that downgrading all the other software updated since then won't break anything else :crossed_fingers: (It didn't on my server)
+1 here. Thanks for the workaround!
Hello, I also have this problem. On one machine, I did a rollback as suggested by the author of the topic - everything works as it should. On another system, I upgraded to the latest version, but unfortunately nothing has changed: It is worth noting that all my docker-based services work fine on this machine, although I do not run them directly, but through . Does anyone reproduce this bug after the "fix" merge, or is it just me who is so "lucky"?

To be honest, the breakdown of such an important basic component as docker surprised me very unpleasantly. I would like more stability and predictability of the software on the servers, but I don't really want to go back to debian :(
Same for me, not working with 23.05.2143. (docker 20.10.25)
I have updated my nixos-23.05 channel that is supposed to have received backported fix by now: However, I still get the same error. I may be missing something, though. Currently, I am using the (not) so yummy hack to soothe the pain: .., and then:
I prefer replacing just docker client with working value like this:
You can also use an overlay in your Nix configuration ( on NixOS) to pin the version of the derivation to an older revision of similar to the comment above:
+1. Still broken for me without the workaround of pinning to an older version.
The linked PR is not in some channel yet, so the status of this hasn't changed and it doesn't help anyone if more people comment that they still have the problem. Please refrain from commenting that. If the PR has landed and the problem isn't fixed yet, please make you heard.
You rather want to use the option .
yes, it has landed, and the problem still isn't fixed. that's why people are commenting. backported the change to 23.05. that change . looking at , that backport went in as on July 19th. on a test box running 23.05, which I just upgraded to make sure I've got the latest from the release channel: []() went in to yesterday (the 21st). so by all accounts the version on my running system should include the backported patch. and yet:
With my solution, only docker client is replaced, not docker daemon.
This is still an issue on 23.05
Confirming that this breakage is currently reproducible on nixos-23.05 but not nixos-unstable. I'm testing with my nixos+flake setup that pulls docker from an flake input as below.

Results testing against relevant revisions:
A patch was missed in the first workaround, see
This seems fixed now (at least in the stable-small channel), so I'm closing this again :)
It's still broken for me on default channel Should I wait some more?
You can track the fix in As you can see it has not yet reached the 23.05 channel
Why are we downgrading go when this issue was already fixed in docker 24.0.5?
We are not downgrading go, we're just patching docker to work with the newer go. These patches will disappear when the docker package is upgraded later
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Still broken for me on release-23.05, after a (nixos.verison 23.05..), even though it seems like this has been backported. EDIT: Looks like it might be a docker vs docker compose issue, works.
That is working for me (not using flake) nixos-version: 23.05.2274.
I observed the same. Docker compose exhibits the issue and Docker doesn’t…
For compose please see and test . Note the issue also likely exist for buildx, the corresponding upstream PR is Feel free to take a look, I will not have time to deal with it before this week end.
works great, thank you!
Bumped into this issue today and my workaround was to build Docker with Go v.1.18 for reasons outlined in and specifying to use the overriden Docker.
My version is still 23.05.2162. - how can I upgrade? (I'm newbie on NixOS)
Now that this has been merged into 23.05, I did a rebuild and this fixed my devcontainers, thank you for the patch. It depends on how you've set up your system, but I'm assuming you're not using flakes. You can also check how to update & manage channels in the (for the inevitable 23.11 release)
It appears is still affected by this.
It worked for me:
Confirmed that this is now resolved for me on branch of at commit .

Same here using , released on 2023-08-14 06:44:13 It is not clear to me if the fix should come from docker/buildx ? does work. Only exposes the issue