Bug 1763210
| Summary: | Udica is broken because changed JSON inspection structure | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Lukas Vrabec <lvrabec> |
| Component: | udica | Assignee: | Lukas Vrabec <lvrabec> |
| Status: | CLOSED WONTFIX | QA Contact: | Milos Malik <mmalik> |
| Severity: | medium | Docs Contact: | Mirek Jahoda <mjahoda> |
| Priority: | high | ||
| Version: | 8.1 | CC: | dwalsh, jligon, jnovy, kanderso, lsm5, mheon, mjahoda, smccarty |
| Target Milestone: | rc | ||
| Target Release: | 8.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
.`udica` processes UBI 8 containers only when started with `--env container=podman`
The Red Hat Universal Base Image 8 (UBI 8) containers set the `container` environment variable to the `oci` value instead of the `podman` value. This prevents the `udica` tool from analyzing a container JavaScript Object Notation (JSON) file.
To work around this problem, start a UBI 8 container using a `podman` command with the `--env container=podman` parameter. As a result, `udica` can generate an SELinux policy for a UBI 8 container only when you use the described workaround.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-15 08:09:34 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 1
Daniel Walsh
2019-10-18 16:45:07 UTC
|