-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CI:DOCS] troubleshooting: add doc for ssh into a container #13197
[CI:DOCS] troubleshooting: add doc for ssh into a container #13197
Conversation
troubleshooting.md
Outdated
|
||
#### Symptom | ||
|
||
ssh running inside the container fails with the error "Error writing /proc/self/loginuid". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/ssh/sshd/
troubleshooting.md
Outdated
|
||
This happens when running Podman from a user session since the | ||
`/proc/self/loginuid` file is already initialized. The solution is to | ||
run Podman from a system service, either using the Podman daemon or |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/Podman daemon/Podman service, and then using podman -remote to start the container.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about this one?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
199614e
to
685ef9a
Compare
@@ -919,3 +919,20 @@ After deleting a client VM on macOS via `podman machine stop` && `podman machine | |||
### 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. | |||
|
|||
### 32) Error writing /proc/self/loginuid: Operation not permitted | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The sshd process fails to run inside of the container. |
troubleshooting.md
Outdated
|
||
#### Symptom | ||
|
||
sshd running inside the container fails with the error "Error writing /proc/self/loginuid". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sshd running inside the container fails with the error "Error writing /proc/self/loginuid". | |
The sshd process running inside the container fails with the error "Error writing /proc/self/loginuid". |
troubleshooting.md
Outdated
`/proc/self/loginuid` file is already initialized. The solution is to | ||
run Podman from a system service, either using the Podman daemon or | ||
simply by running something like `systemd-run podman run ...`. In | ||
this case the container will only need `CAP_AUDIT_WRITE`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a blog about this that we could add a link to here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, no blog post about this error
Signed-off-by: Giuseppe Scrivano <[email protected]>
685ef9a
to
a0b38c0
Compare
/lgtm |
This happens when running Podman from a user session since the | ||
`/proc/self/loginuid` file is already initialized. The solution is to | ||
run Podman from a system service, either using the Podman service, and | ||
then using podman -remote to start the container or simply by running |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
podman -remote
Could it be
podman-remote
or maybe
podman --remote ...
?
Signed-off-by: Giuseppe Scrivano [email protected]