diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2022-01-27 09:44:50 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-27 09:44:50 -0500 |
| commit | 5d6b5a03557385e1a0d6d6ecc29522b0101e22dd (patch) | |
| tree | 565f984b4e81d6712d8cc074a2b3e772d20216c8 | |
| parent | 9e7e91c13e32fc5897b336dbed8df1fd060a3ac4 (diff) | |
| parent | 86547cc24a67216945ef2245b4f6290a3b18e1ea (diff) | |
| download | podman-5d6b5a03557385e1a0d6d6ecc29522b0101e22dd.tar.gz podman-5d6b5a03557385e1a0d6d6ecc29522b0101e22dd.tar.bz2 podman-5d6b5a03557385e1a0d6d6ecc29522b0101e22dd.zip | |
Merge pull request #13035 from rhatdan/docs1
CI:DOCS: Add troublshooting info on podman machine remove followed by podman machine init
| -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. |