mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-11-03 09:37:34 +00:00
d7bc7b7b41
we are having second thoughts about *requiring* a policy.json on podman machine hosts. we are concerned that we need to work out some more use cases to be sure we do not make choices now that limit us in the near term future. for example, should the policy files be the same for container images and machine images? And should one live on the host machine and the other live in the machine? therefore, if a policy.json *is* present in the correct location, we will use and honor it; however, if it does not, we will allow the machine image to be pulled without a policy. Signed-off-by: Brent Baude <baude@redhat.com> Co-authored-by: Paul Holzinger <45212748+Luap99@users.noreply.github.com> Signed-off-by: Brent Baude <bbaude@redhat.com> |
||
|---|---|---|
| .. | ||
| cirrus | ||
| containers-common | ||
| hello | ||
| modules-load.d | ||
| pkginstaller | ||
| podman-next/fcos-podmanimage | ||
| podmanimage | ||
| remote | ||
| script | ||
| snapcraft | ||
| systemd | ||
| tmpfile | ||
| win-installer | ||
| dependabot-dance | ||
| dependencies.txt | ||