-
Notifications
You must be signed in to change notification settings - Fork 199
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
containers.conf should be cached #1200
Comments
The default call is already cached: Line 1165 in c73d138
This means that the callers do not use it and call NewConfig("") instead. |
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Oct 20, 2022
We should not be changing these fields on the client side unless the user specified them. This patch drops strace mentions of containers.conf from 116 down to 26. Fixes: containers/common#1200 [NO NEW TESTS NEEDED] Existing tests should test this. Signed-off-by: Daniel J Walsh <[email protected]>
vrothberg
added a commit
to vrothberg/libpod
that referenced
this issue
Oct 21, 2022
Use `Default()` instead of re-loading containers.conf. Also rework how the containers.conf objects are handled for parsing the CLI. Previously, we were conflating "loading the defaults" with "storing values from the CLI" with "libpod may further change fields" which ultimately led to various bugs and test failues. To address the issue, separate the defaults from the values from the CLI and properly name the fields to make the semantics less ambiguous. [NO NEW TESTS NEEDED] as it's not a functional change. Fixes: containers/common/issues/1200 Signed-off-by: Valentin Rothberg <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The below strace suggests that containers.conf should be cached. We are already doing that for registries.conf. The idea for registries.conf was to cache directly in the package to prevent users from having to take care of caching. SIGHUB can be used to trigger reloads (as done with cri-o).
The text was updated successfully, but these errors were encountered: