-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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] Add --userns=keep-id, --uidmap, --gidmap troubleshooting #13084
[CI:DOCS] Add --userns=keep-id, --uidmap, --gidmap troubleshooting #13084
Conversation
9ad1d48
to
ab1c0b0
Compare
troubleshooting.md
Outdated
@@ -919,3 +919,113 @@ 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) Passed-in devices or files can't be accessed in rootless container or a container creates files that can't be accessed by the regular user on the host |
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.
These should be broken into two separate examples. Putting them into 1 is confusing to me.
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.
You're right. I split them in two.
a172ef8
to
8bd0698
Compare
Thanks @TomSweeneyRedHat for the feedback. I'll have a look during the weekend. The state of the text is still somewhat in a flow. The big picture of what I intend to put in the PR is there, but I might change a few things. |
I noticed that
describe different permission denied problems.
https://github.com/eriksjolund/podman/blob/restructure_permission_denied_troubleshooting_tips/troubleshooting.md In the other branch I also modified text regarding "Jupyter Notebook container" and "Postgres image" was modified. |
4bf6dba
to
d836ea4
Compare
You have to fix your trailing whitespace. |
d836ea4
to
0c431b0
Compare
Fixed |
* Add troubleshooting advice: "Container creates a file that is not owned by the user's regular UID". The solution involves using the options --uidmap and --gidmap. * Add troubleshooting advice: "Passed-in devices or files can't be accessed in rootless container (UID/GID mapping problem)". The general solution involves using the options --uidmap and --gidmap. Sometimes --userns=keep-id could be used. Co-authored-by: Tom Sweeney <[email protected]> Signed-off-by: Erik Sjölund <[email protected]>
0c431b0
to
3b5a3f4
Compare
I force pushed a new version that added a few sentences "Would it have been possible to run Podman in another way ..." |
/approve |
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.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eriksjolund, 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 |
/lgtm |
and --gidmap : "Passed-in devices or files can't be accessed in
rootless container or a container creates files that can't be
accessed by the regular user on the host"
Signed-off-by: Erik Sjölund [email protected]