Skip to content
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

Merged

Conversation

giuseppe
Copy link
Member

Signed-off-by: Giuseppe Scrivano [email protected]

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2022

#### Symptom

ssh running inside the container fails with the error "Error writing /proc/self/loginuid".
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/ssh/sshd/


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
Copy link
Member

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about this one?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2022

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@giuseppe giuseppe force-pushed the doc-cannot-write-loginuid branch from 199614e to 685ef9a Compare February 10, 2022 14:23
@@ -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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The sshd process fails to run inside of the container.


#### Symptom

sshd running inside the container fails with the error "Error writing /proc/self/loginuid".
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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".

`/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`.
Copy link
Member

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?

Copy link
Member Author

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

@giuseppe giuseppe force-pushed the doc-cannot-write-loginuid branch from 685ef9a to a0b38c0 Compare February 10, 2022 16:09
@rhatdan
Copy link
Member

rhatdan commented Feb 10, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 10, 2022
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
Copy link
Contributor

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 ...
?

@openshift-merge-robot openshift-merge-robot merged commit 6d2b54a into containers:main Feb 10, 2022
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants