From 1a1c1217e991f1a5e2370a759830971869463a38 Mon Sep 17 00:00:00 2001 From: Marcus Noble Date: Wed, 1 Sep 2021 18:51:26 +0100 Subject: [PATCH] Added note about socket bug PR --- src/posts/2021-09-01-migrating-from-docker-to-podman.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/posts/2021-09-01-migrating-from-docker-to-podman.md b/src/posts/2021-09-01-migrating-from-docker-to-podman.md index f3f52a6..954658c 100644 --- a/src/posts/2021-09-01-migrating-from-docker-to-podman.md +++ b/src/posts/2021-09-01-migrating-from-docker-to-podman.md @@ -8,6 +8,12 @@ summary: "Docker has [recently announced](https://www.docker.com/blog/updating-p There has been quite a bit of reaction to this news..." --- +
+Changelog + +2021-09-01: Added note about socket bugfix PR +
+ Docker has [recently announced](https://www.docker.com/blog/updating-product-subscriptions/) that Docker Desktop will soon require a subscription and, based on the size of your company, may require a paid subscription. (It remains free for personal use) There has been quite a bit of reaction to this news: @@ -90,6 +96,8 @@ panic: interface conversion: net.Conn is nil, not *net.UnixConn This seems to happen (for me at least) when I've previously run `podman machine stop`. It looks like the sock file isn't correctly being removed. Doing an `rm` on that file mentioned in the error message will be enough to get you going again. +> UPDATE: Looks like this will be fixed in an upcoming release. - [PR](https://github.com/containers/podman/pull/11342) + ```sh Error: error creating build container: short-name resolution enforced but cannot prompt without a TTY ```