From 86547cc24a67216945ef2245b4f6290a3b18e1ea Mon Sep 17 00:00:00 2001 From: bazhang87 <60352611+bazhang87@users.noreply.github.com> Date: Tue, 18 Jan 2022 11:36:48 -0600 Subject: Update troubleshooting.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Bart Zhang bazhang@redhat.com Co-authored-by: Erik Sjölund Co-authored-by: Tom Sweeney Signed-off-by: Daniel J Walsh --- troubleshooting.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) 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 ` * If `loginctl` is unavailable you can also try logging in via `ssh` i.e `ssh @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. -- cgit v1.2.3-54-g00ecf