diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2019-02-06 23:44:17 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-02-06 23:44:17 +0100 |
| commit | 0cf9747cf4fae160f1335395c41595461fdb4866 (patch) | |
| tree | c282f70919e23259c89ad0d0cfce3a42c6c48053 | |
| parent | 74e71c41d28dc1b029a9af68fa48e0f830983ce7 (diff) | |
| parent | a216c87150d3b68815ead3557e3acea946dc1724 (diff) | |
| download | podman-0cf9747cf4fae160f1335395c41595461fdb4866.tar.gz podman-0cf9747cf4fae160f1335395c41595461fdb4866.tar.bz2 podman-0cf9747cf4fae160f1335395c41595461fdb4866.zip | |
Merge pull request #2237 from fulldecent/patch-1
Mention officially supported OSes, fixes #2208
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -20,6 +20,8 @@ At a high level, the scope of libpod and podman is the following: * Resource isolation of containers and pods. * Integration with CRI-O to share containers and backend code. +This project tests all builds against each supported version of Fedora, the latest released version of Red Hat Enterprise Linux, and the latest Ubuntu Long Term Support release. The community has also reported success with other Linux flavors. + ## Roadmap 1. Allow the Podman CLI to use a Varlink backend to connect to remote Podman instances |