[roll] Roll fuchsia [sestarnix] Fail component launches without Security Context

If the Starnix container has SELinux configured then either the
container or the component must specify the Security Context under
which it should run. This removes the fall-back to inheriting the
Security Context of the init process, which is invariably not what
the component author expects.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1271005
Original-Revision: 333e3a9a93a7bd6b367c14d828c7205c1731f0be
GitOrigin-RevId: 4a6f754bc90243ff943b33f2392fa0f6a71c88af
Change-Id: I88bada96b234b22a96e6747c67f306576db91d51
1 file changed
tree: 82912b68a4b6753a5dbc1a75ab8c1721cc716fda
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.