diff options
| author | bazhang87 <60352611+bazhang87@users.noreply.github.com> | 2022-01-18 11:36:48 -0600 |
|---|---|---|
| committer | Daniel J Walsh <dwalsh@redhat.com> | 2022-01-27 07:45:11 -0500 |
| commit | 86547cc24a67216945ef2245b4f6290a3b18e1ea (patch) | |
| tree | 621618e4822490637b42d93dbbc172776d22bbd1 /troubleshooting.md | |
| parent | 0d96c46c7c4de3f4464e8d55b6134b9bd082cf34 (diff) | |
| download | podman-86547cc24a67216945ef2245b4f6290a3b18e1ea.tar.gz podman-86547cc24a67216945ef2245b4f6290a3b18e1ea.tar.bz2 podman-86547cc24a67216945ef2245b4f6290a3b18e1ea.zip | |
Update troubleshooting.md
Signed-off-by: Bart Zhang bazhang@redhat.com
Co-authored-by: Erik Sjölund <erik.sjolund@gmail.com>
Co-authored-by: Tom Sweeney <tsweeney@redhat.com>
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'troubleshooting.md')
| -rw-r--r-- | troubleshooting.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/troubleshooting.md b/troubleshooting.md index 114a96d41..82ca64305 100644 --- a/troubleshooting.md +++ b/troubleshooting.md @@ -907,3 +907,15 @@ Resolution steps * Before invoking Podman command create a valid login session for your rootless user using `loginctl enable-linger <username>` * If `loginctl` is unavailable you can also try logging in via `ssh` i.e `ssh <username>@localhost`. + +### 31) 127.0.0.1:7777 port already bound + +After deleting a VM on macOS, the initialization of subsequent VMs fails. + +#### Symptom + +After deleting a client VM on macOS via `podman machine stop` && `podman machine rm`, attempting to `podman machine init` a new client VM leads to an error with the 127.0.0.1:7777 port already bound. + +### Solution + +You will need to remove the hanging gv-proxy process bound to the port in question. For example, if the port mentioned in the error message is 127.0.0.1:7777, you can use the command `kill -9 $(lsof -i:7777)` in order to identify and remove the hanging process which prevents you from starting a new VM on that default port. |