LawrenceHunter opened a new issue, #2080:
URL: https://github.com/apache/buildstream/issues/2080

   Builds do not work on macOS inside containers, specifically when going 
cross-arch through the Podman VM.
   
   ## Rootful VM
   
   ```
   # Install brew, podman, & podman-compose
   podman machine init --rootful
   podman machine start
   podman run --privileged --rm tonistiigi/binfmt --install all
   
   podman run -it \
       --privileged \
       --platform=linux/amd64 \
       --volume ~/.cache/buildstream:/root/.cache/buildstream \
       --volume $(pwd):/src \
       --security-opt apparmor=unconfined \
       --security-opt seccomp=unconfined \
       --workdir /src \
       bst:latest \
       /bin/bash -c "\
           source /myenv/bin/activate && \
           bst build gnomeos/live-image.bst && \
           bst artifact checkout gnomeos/live-image.bst --directory ./iso \
       "
   
   >  bwrap: Creating new namespace failed, likely because the kernel does not 
support user namespaces.  bwrap must be installed setuid on such systems.
   ```
   
   ## Rootless VM
   
   ```
   # Install brew, podman, & podman-compose
   podman machine init 
   podman machine init
   podman machine start
   podman machine ssh
   $ sudo -i
   $ rpm-ostree install qemu-user-static
   $ systemctl reboot
   
   podman run -it \
       --privileged \
       --platform=linux/amd64 \
       --volume ~/.cache/buildstream:/root/.cache/buildstream \
       --volume $(pwd):/src \
       --security-opt apparmor=unconfined \
       --security-opt seccomp=unconfined \
       --userns=keep-id \
       --workdir /src \
       bst:latest \
       /bin/bash -c "\
           source /myenv/bin/activate && \
           bst build gnomeos/live-image.bst && \
           bst artifact checkout gnomeos/live-image.bst --directory ./iso \
       "
   
   > bwrap: Unexpected capabilities but not setuid, old file caps config?
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to