| |
@@ -28,6 +28,19 @@
|
| |
_Requirement_: Installation must occur in the same locations as
|
| |
traditional RPM software delivery.
|
| |
|
| |
+ === Trust your containers
|
| |
+
|
| |
+ As Linux containers grow more popular, the number of disreputable
|
| |
+ images on container registries has also been rising. Delivering
|
| |
+ trustworthy binaries to users is something that traditional
|
| |
+ distributions have always done well. They provide assurance (in the
|
| |
+ form of signatures, Secure Boot and other trusted delivery paths) that
|
| |
+ the software you’re running is the software you think it is.
|
| |
+
|
| |
+ _Requirement_: It must be possible for users to construct container
|
| |
+ images based on Fedora content matching the software version they need
|
| |
+ for their applications.
|
| |
+
|
| |
=== Don’t break the app!
|
| |
|
| |
It is very common for Fedora to update to the latest major version of
|
| |
