Post restructuring (headings)

This commit is contained in:
Marcus Noble 2021-09-01 20:08:22 +01:00
parent de320346e3
commit d7ccad274c

View File

@ -84,12 +84,16 @@ So, lets give it a whirl...
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...
### Failed to parse config
```sh ```sh
Error: failed to parse query parameter 'X-Registry-Config': "n/a": error storing credentials in temporary auth file (server: "https://index.docker.io/v1/", user: ""): key https://index.docker.io/v1/ contains http[s]:// prefix Error: failed to parse query parameter 'X-Registry-Config': "n/a": error storing credentials in temporary auth file (server: "https://index.docker.io/v1/", user: ""): key https://index.docker.io/v1/ contains http[s]:// prefix
``` ```
Podman seems more strict than Docker when parsing the config file, check the `~/.docker/config.json` file for the key with the `https://` prefix (as mentioned in the error message) and remove it. Podman seems more strict than Docker when parsing the config file, check the `~/.docker/config.json` file for the key with the `https://` prefix (as mentioned in the error message) and remove it.
### Sock already exists
```sh ```sh
✨ podman machine start ✨ podman machine start
ERRO[0000] "/var/folders/x_/bfc7v6kn4fs0rl9k77whs0nw0000gn/T/podman/qemu_podman-machine-default.sock" already exists ERRO[0000] "/var/folders/x_/bfc7v6kn4fs0rl9k77whs0nw0000gn/T/podman/qemu_podman-machine-default.sock" already exists
@ -100,6 +104,8 @@ 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)
### Automatic published port forwarding
```sh ```sh
✨ podman run --rm -it --publish 8000:80 docker.io/library/nginx:latest & ✨ podman run --rm -it --publish 8000:80 docker.io/library/nginx:latest &
✨ curl http://localhost:8000 ✨ curl http://localhost:8000
@ -121,14 +127,14 @@ The other, more perminant option is to add `rootless_networking = "cni"` under t
To follow the progress of this bug, please refer to the [issue](https://github.com/containers/podman/issues/11396). To follow the progress of this bug, please refer to the [issue](https://github.com/containers/podman/issues/11396).
## short-name resolution
```sh ```sh
Error: error creating build container: short-name resolution enforced but cannot prompt without a TTY Error: error creating build container: short-name resolution enforced but cannot prompt without a TTY
``` ```
Ok, this is the big one and the major issue you'll likely hit making the switch today from Docker to Podman. Lets dive into it in a bit more detail... Ok, this is the big one and the major issue you'll likely hit making the switch today from Docker to Podman. Lets dive into it in a bit more detail...
## short-name resolution
First we need to understand what a short-name is in this context. It refers to container images that don't have a full domain name prefixed. You've likely come across these quite a lot before - e.g. `alpine:latest`, `ubuntu:12`, `giantswarm/pause:latest`, etc. First we need to understand what a short-name is in this context. It refers to container images that don't have a full domain name prefixed. You've likely come across these quite a lot before - e.g. `alpine:latest`, `ubuntu:12`, `giantswarm/pause:latest`, etc.
When using Docker, these images are actually first prefixed with `docker.io` (or `docker.io/library` for those official images without a namespace) before being pulled. When using Docker, these images are actually first prefixed with `docker.io` (or `docker.io/library` for those official images without a namespace) before being pulled.