Quick Start Fails on Master Branch

[jshlbrd]

Describe the bug
Step 4 of the quickstart isn't working for me:

failed to solve: executor failed running [/bin/sh -c apt-get -q update && apt-get install -q -y --no-install-recommends automake build-essential cmake curl gcc git gpg libglu1-mesa libtool make swig python3-dev python3-pip python3-wheel python-is-python3 pkg-config]: exit code: 100

This is also in the output:

 > [ 5/19] RUN apt-get -q update &&     apt-get install -q -y --no-install-recommends     automake     build-essential     cmake     curl     gcc     git     gpg     libglu1-mesa     libtool     make     swig     python3-dev     python3-pip     python3-wheel     python-is-python3     pkg-config:  
#0 0.498 Get:1 http://archive.ubuntu.com/ubuntu kinetic InRelease [267 kB]                                                                           
#0 0.499 Get:2 http://ports.ubuntu.com/ubuntu-ports jammy InRelease [270 kB]                                                                         
#0 1.397 Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [114 kB]                                                                 
#0 1.602 Ign:4 http://archive.ubuntu.com/ubuntu kinetic/multiverse arm64 Packages
#0 1.612 Get:5 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease [99.8 kB]
#0 1.800 Ign:6 http://archive.ubuntu.com/ubuntu kinetic/universe arm64 Packages
#0 1.802 Ign:7 http://archive.ubuntu.com/ubuntu kinetic/main arm64 Packages
#0 1.802 Ign:8 http://archive.ubuntu.com/ubuntu kinetic/restricted arm64 Packages
#0 1.837 Get:9 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
#0 1.971 Ign:4 http://archive.ubuntu.com/ubuntu kinetic/multiverse arm64 Packages
#0 1.972 Ign:6 http://archive.ubuntu.com/ubuntu kinetic/universe arm64 Packages
#0 1.972 Ign:7 http://archive.ubuntu.com/ubuntu kinetic/main arm64 Packages
#0 2.056 Get:10 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages [17.2 MB]
#0 2.130 Ign:8 http://archive.ubuntu.com/ubuntu kinetic/restricted arm64 Packages
#0 2.130 Ign:4 http://archive.ubuntu.com/ubuntu kinetic/multiverse arm64 Packages
#0 2.131 Ign:6 http://archive.ubuntu.com/ubuntu kinetic/universe arm64 Packages
#0 2.286 Ign:7 http://archive.ubuntu.com/ubuntu kinetic/main arm64 Packages
#0 2.286 Ign:8 http://archive.ubuntu.com/ubuntu kinetic/restricted arm64 Packages
#0 2.286 Ign:4 http://archive.ubuntu.com/ubuntu kinetic/multiverse arm64 Packages
#0 2.443 Ign:6 http://archive.ubuntu.com/ubuntu kinetic/universe arm64 Packages
#0 2.443 Ign:7 http://archive.ubuntu.com/ubuntu kinetic/main arm64 Packages
#0 2.443 Ign:8 http://archive.ubuntu.com/ubuntu kinetic/restricted arm64 Packages
#0 2.595 Ign:4 http://archive.ubuntu.com/ubuntu kinetic/multiverse arm64 Packages
#0 2.597 Ign:6 http://archive.ubuntu.com/ubuntu kinetic/universe arm64 Packages
#0 2.597 Ign:7 http://archive.ubuntu.com/ubuntu kinetic/main arm64 Packages
#0 2.751 Ign:8 http://archive.ubuntu.com/ubuntu kinetic/restricted arm64 Packages
#0 2.755 Err:4 http://archive.ubuntu.com/ubuntu kinetic/multiverse arm64 Packages
#0 2.755   404  Not Found [IP: 185.125.190.36 80]
#0 2.755 Ign:6 http://archive.ubuntu.com/ubuntu kinetic/universe arm64 Packages
#0 2.914 Ign:7 http://archive.ubuntu.com/ubuntu kinetic/main arm64 Packages
#0 2.914 Ign:8 http://archive.ubuntu.com/ubuntu kinetic/restricted arm64 Packages
#0 3.669 Get:11 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages [1758 kB]
#0 3.670 Get:12 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse arm64 Packages [224 kB]
#0 3.670 Get:13 http://ports.ubuntu.com/ubuntu-ports jammy/restricted arm64 Packages [24.2 kB]

Steps to reproduce
Steps to reproduce the behavior:
Follow the Quickstart.

Expected behavior
Docker containers build correctly.

Screenshots
N/A

Release

• Release: master / main

Additional context
Appears that the latest release from December 8th 2022 works correctly.

[phutelmyer]

Hi @jshlbrd - hope you're doing well!

I can confirm that this build error is seemingly exclusive to builds on ARM processors. I'm currently working on a fix (was able to resolve the above, but hitting a different error now).

We're planning on hosting precompiled images in the near future to remove the need for users to compile their own images.

I'll tag you when either occurs.
Thanks for the report!

[jshlbrd]

Ahh ARM, makes sense since I'm building on an M1. Thanks for keeping this thing alive! 🫡

[phutelmyer]

Fix for ARM compilation: 5c6f776

[phutelmyer]

@jshlbrd - This should be fixed in #289. Was tested with an M1.

Please reopen if you're still having issues.

[jshlbrd]

Thanks @phutelmyer! Looks like that solved the ARM build issues. It's failing on pytest, which is a separate issue that I can see is being worked on by @ryanohoro.

[phutelmyer]

Yup fixed in #291