Compare commits

..

No commits in common. "36a58be0f15071058ef2231f569c620a1416ef00" and "c10c858988ede79f11bd41beec012c4c96d71d09" have entirely different histories.

2 changed files with 2 additions and 29 deletions

View File

@ -1,6 +1,6 @@
.DEFAULT_GOAL := default .DEFAULT_GOAL := default
IMAGE ?= docker.cluster.fun/averagemarcus/blog:latest IMAGE ?= docker.cloud.cluster.fun/averagemarcus/blog:latest
.PHONY: test # Run all tests, linting and format checks .PHONY: test # Run all tests, linting and format checks
test: lint check-format run-tests test: lint check-format run-tests

View File

@ -14,14 +14,6 @@ There has been quite a bit of reaction to this news..."
2021-09-01: Added note about socket bugfix PR 2021-09-01: Added note about socket bugfix PR
2021-09-01: Added troubleshooting section about port forwarding bug 2021-09-01: Added troubleshooting section about port forwarding bug
2021-09-04: Added note about switching to Podman on Windows
2021-09-04: Added update about port forwarding PR
2021-09-04: Added note about M1 Mac support
2021-09-04: Added volume mount limitation
</details> </details>
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) 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)
@ -58,8 +50,6 @@ So, lets give it a whirl...
## Replacing Docker with Podman (on Mac) ## Replacing Docker with Podman (on Mac)
> Note: This currently doesn't work for Macs with an M1 CPU. I've come across this post in my search - [Running Podman Machine on the Mac M1](https://www.cloudassembler.com/post/podman-machine-mac-m1/) - but I've not confirmed if it works or not.
1. `brew install podman` 1. `brew install podman`
2. Wait while brew downloads, builds and installs... 2. Wait while brew downloads, builds and installs...
3. Create a virtual machine for Podman to run from: 3. Create a virtual machine for Podman to run from:
@ -90,10 +80,6 @@ So, lets give it a whirl...
5. `alias docker=podman` (Add this to your `.bashrc` (if using Bash), `.zshrc` (if using ZSH) or whatever the correct file for your shell is) 5. `alias docker=podman` (Add this to your `.bashrc` (if using Bash), `.zshrc` (if using ZSH) or whatever the correct file for your shell is)
6. 🎉 6. 🎉
## Replacing Docker with Podman (on Windows)
I don't currently have access to a Windows machine where I can test this out but [Frank](https://twitter.com/frank_k_p) sent me this [on Twitter](https://twitter.com/frank_k_p/status/1433490007088668672) that covers the process needed for those on Windows with WLS2 - [How to run Podman on Windows with WSL2](https://www.redhat.com/sysadmin/podman-windows-wsl2).
## Troubleshooting ## Troubleshooting
Ok, so it's not all *completely* pain free, there are a few issues you might hit... Ok, so it's not all *completely* pain free, there are a few issues you might hit...
@ -118,19 +104,6 @@ This seems to happen (for me at least) when I've previously run `podman machine
> UPDATE: Looks like this will be fixed in an upcoming release. - [PR](https://github.com/containers/podman/pull/11342) > UPDATE: Looks like this will be fixed in an upcoming release. - [PR](https://github.com/containers/podman/pull/11342)
### Volume mounts
```sh
✨ podman run --rm -it -v $(pwd):/usr/share/nginx/html:ro --publish 8000:80 docker.io/library/nginx:latest
Error: statfs /Users/marcus/web: no such file or directory
```
Podman machine currently has now support for mounting volumes from the host machine (your Mac) into the container on the virtual machine. Instead, it attepts to mount a directory matching what you specified from the _virtual machine_ rather than your Mac.
This is a fairly big issue if you're looking for a smooth transition from Docker Desktop.
There's currently a fairly active [issue](https://github.com/containers/podman/issues/8016) about this limitation but as of right now there doesn't seem to be a nice workaround or solution.
### Automatic published port forwarding ### Automatic published port forwarding
```sh ```sh
@ -152,7 +125,7 @@ The first is passing in the `--network bridge` flag to the podman command, e.g.
The other, more perminant option is to add `rootless_networking = "cni"` under the `[containers]` section of your `~/.config/containers/containers.conf` file. The other, more perminant option is to add `rootless_networking = "cni"` under the `[containers]` section of your `~/.config/containers/containers.conf` file.
To follow the progress of this bug, please refer to the [issue](https://github.com/containers/podman/issues/11396). **UPDATE**: This has now been merged and is expected to be released in v3.3.2 in the next few days or so. To follow the progress of this bug, please refer to the [issue](https://github.com/containers/podman/issues/11396).
## short-name resolution ## short-name resolution