Use --privileged in Fedora container

This enables the namespace-based sandbox in Bazel.

Using `--privileged` isn't as dangerous as it looks, when used with podman in rootless mode (i.e. ran as unprivileged user), in which case it uses user namespaces.

We drop `--net=host`, which is not actually necessary.

Test Plan:
    scripts/destroy_container.sh
    scripts/create_container.sh
    scripts/run_in_container.sh bazelisk build :swtpm_data

 This now fails properly when ran with the container:

     swtpm-localca: touch: cannot touch '/var/lib/swtpm-localca/.lock.swtpm-localca': Read-only file system
     swtpm-localca: Error: Could not create lock file /var/lib/swtpm-localca/.lock.swtpm-localca.

X-Origin-Diff: phab/D202
GitOrigin-RevId: f51a831e7584cccf21860e9f18b73272a658f055
1 file changed
tree: 73b7533e0ba991eb8f2d98ed58e4350ca4c8e394
  1. build/
  2. cmd/
  3. internal/
  4. pkg/
  5. scripts/
  6. .bazelignore
  7. .bazelrc
  8. .bazelversion
  9. BUILD
  10. README.md
  11. WORKSPACE
README.md

Smalltown Operating System

Run build

The build uses a Fedora 30 base image with a set of dependencies. Guide has been tested on a Fedora 30 host, with latest rW deployed.

Build the base image:

podman build -t smalltown-builder .

Launch the VM:

scripts/bin/bazel run scripts:launch

Exit qemu using the monitor console: Ctrl-A c quit.