Bug 1826486
| Summary: | specfile: need to include and ship containers.conf | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Ed Santiago <santiago> |
| Component: | skopeo | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.2 | CC: | dwalsh, gnecasov, jnovy, kanderso, tsweeney, yujiang |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | skopeo-0.2.0-3.el8 | Doc Type: | Enhancement |
| Doc Text: |
.Configuration file `container.conf` is now available
With this enhancement, users and administrators can specify default configuration options and command-line flags for container engines. Container engines read the `/usr/share/containers/containers.conf` and `/etc/containers/containers.conf` files if they exist. In the rootless mode, container engines read the `$HOME/.config/containers/containers.conf` files.
Fields specified in the `containers.conf` file override the default options, as well as options in previously read `containers.conf` files. The `container.conf` file is shared between Podman and Buildah and replaces the `libpod.conf` file.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-21 15:31:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 5
Daniel Walsh
2020-04-23 10:43:56 UTC
We should not be shipping an /etc/containers/containers.conf, we can ghost it though. This is how it's declared in spec:
%ghost %{_sysconfdir}/containers/containers.conf
It is expected then - %ghost files are just owned but not shipped.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3053 |