-
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
update configuration for rootless podman #6954
Conversation
@@ -106,8 +106,31 @@ Once the Administrator has completed the setup on the machine and then the confi | |||
|
|||
### User Configuration Files | |||
|
|||
The Podman configuration files for root reside in `/usr/share/containers` with overrides in `/etc/containers`. In the rootless environment they reside in `${XDG_CONFIG_HOME}/containers` (usually `~/.config/containers`) and are owned by each individual user. The main files are `libpod.conf` and `storage.conf` and the user can modify these files as they wish. | |||
The three main configuration files are `containers.conf`, `storage.conf` and `registries.conf`. | |||
#### containers.conf |
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.
Can you add an extra blank line before this header?
docs/tutorials/rootless_tutorial.md
Outdated
2. `/etc/containers/registries.d/*` | ||
3. `HOME/.config/containers/registries.conf` | ||
|
||
The files in the home directory should be used to configure rootless podman for personal needs. These files do not exist by default. Users can copy the files from `/usr/share/containers` or `/etc/containers` and modify them. |
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.
Suggest rephrasing: "do not exist by default" -> "are not created by default"
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gatoniel, mheon 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 |
Thanks for the contribution! Your commit appears to be missing a signoff - can you run |
Sorry for the mess. There should now be a signoff. |
2. `/etc/containers/registries.d/*` | ||
3. `HOME/.config/containers/registries.conf` | ||
|
||
The files in the home directory should be used to configure rootless podman for personal needs. These files are not created by default. Users can copy the files from `/usr/share/containers` or `/etc/containers` and modify them. |
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.
I thought some of these files were created by default for a rootless user in their home directory?
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.
Not any longer.
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.
Perhaps we should create the directories. The problem with creating the files, is we ended up hard coding some defaults that we later changed, and users ended up with bad files in their homedirs, which we could not change.
@gatoniel You need to rebase and squash your commits as well as sign them git rebase -i origin |
docs/tutorials/rootless_tutorial.md
Outdated
1. `/etc/containers/storage.conf` | ||
2. `$HOME/.config/containers/storage.conf` | ||
|
||
In rootless podman certain fields in `/etc/containers/storage.conf` are ignored. |
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.
We should list the fields that are ignored.
graphroot=""
container storage graph dir (default: "/var/lib/containers/storage")
Default directory to store all writable content created by container storage programs.
runroot=""
container storage run dir (default: "/var/run/containers/storage")
Default directory to store all temporary writable content created by container storage programs.
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.
I suggest adding their default values, when in rootless podman. (see new commits). I do not exactly know, if podman really reads out $XDG_RUNTIME_DIR or just defaults to /run/user/$UID
.
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.
It uses XDG_RUNTIME_DIR
BTW @gatoniel Nice work. |
You really need to squash your commits and sign the one commit, to get it past the gating test. |
7cc4f87
to
6211a5a
Compare
@gatoniel still working on this? Needs a rebase and to squash your commits. |
I am so sorry for taking your time. I have never used the rebase before. Now I swapped pick -> squash . I hope that´s correct. How can I resolve the build_each_commit fail? |
Sadly still needs a rebase. |
@gatoniel Sadly one more rebase. |
I updated the configuration part of the tutorial on rootless podman. I added the order in which configuration files are read in and a hint, how users can create default configuration in the home directories. Closes containers#6777 Signed-off-by: Niklas Netter <[email protected]>
I do not think this is a rebase issue. There is always an auto-merging conflict. I now resolved the auto-merging conflict by using Githubs PR resolver, this added the new commit. The tide test is now pending instead of failing. But build_each_commit is still failing with this error message
I really do not know what to do. |
I updated the configuration part of the tutorial on rootless podman. I added the order in which configuration files are read in and a hint, how users can create default configuration in the home directories.
Closes #6777
Signed-off-by: Niklas Netter [email protected]