ag123

@Gunjan Gupta Thanks, and a new guide/tutorial Building Armbian using Ubuntu (jammy) in a systemd-nspawn container https://gist.github.com/ag88/05245121cce37cb8f029424a20752e35

Building Armbian using Ubuntu (jammy) in a systemd-nspawn container https://gist.github.com/ag88/05245121cce37cb8f029424a20752e35 Special thanks goes to @Gunjan Gupta for the tip on PREFER_DOCKER=no

thanks Gunjan Gupta, yeah, I'd need to upgrade the distribution, has posponed it for a very long time. A trouble is I've got a lot of other stuff installed in the same system, though in different partitions / filesystems. An upgrade would likely break quite a few stuff, hence I'd need to schedule that.

keys that promts with NO_PUBKEY errors can be manually retrieved like such use a keyserver e.g. https://keyserver.ubuntu.com/ key in the PUBKEY and search/retrieve the public key looks like this https://keyserver.ubuntu.com/pks/lookup?search=23F3D4EA75716059&fingerprint=on&op=index you can probably download that (an asc file, clicking on the pub link. That is the public key in an 'armored ascii' format and perhaps use https://8gwifi.org/pgpdump.jsp to dump/verify it again. the key (the .asc file) can be converted and installed for apt as in the prior comment.

I'm not sure if some hints from here may help, especially the initial post. it probably works if the public key is not expired (e.g. has no expiry dates).

hi Gunjan Gupta, thanks much! PREFER_DOCKER=no works in the systemd-nspawn Ubuntu Jammy 22.04 container that I created to run compile.sh for reasons I couldn't figure out, I did not manage to resolve the NO PUBKEY errors running in a docker container. but that the run proceed significantly without issues doing apt-get update, apt-get install and all with PREFER_DOCKER=no

I tried downloading the keys https://keyserver.ubuntu.com/pks/lookup?search=871920D1991BC93C&fingerprint=on&op=index and following this https://askubuntu.com/questions/1286545/what-commands-exactly-should-replace-the-deprecated-apt-key generated a gpg key file, placed it in /etc/apt/trusted.gpg.d the keys can be checked using apt-key list but that it didn't seem to fix the problem when run from a docker container. Apparently, the userid that docker build used to run apt-get update and apt-get install ... , is not root, and there are errors reading the gpg key files. It could be due to an older docker engine that I'm running. The docker client is from Ubuntu jammy 22.04

there is a different problem https://keyserver.ubuntu.com/pks/lookup?search=871920D1991BC93C&fingerprint=on&op=index Type bits/keyID cr. time exp time key expir pub (4)rsa4096/f6ecb3762474eda9d21b7022871920d1991bc93c 2018-09-17T15:01:46Z uid Ubuntu Archive Automatic Signing Key (2018) <ftpmaster@ubuntu.com> sig sig 871920d1991bc93c 2018-09-17T15:01:46Z ____________________ ____________________ [selfsig] sig sig 0bfb847f3f272f5b 2018-09-17T15:12:03Z ____________________ ____________________ 0bfb847f3f272f5b sig sig 7de50a8278ddc1f0 2021-12-06T22:39:23Z ____________________ ____________________ 7de50a8278ddc1f0 the public key used to sign the files is apparently expired. This is strange as then all the apt-get install commands will fail. edit: nope doesn't seem so https://8gwifi.org/pgpdump.jsp Key ID: 871920d1991bc93c Algorithm: RSA_GENERAL Fingerprint: f6ecb3762474eda9d21b7022871920d1991bc93c Encoded: 99020d045b9fc1da011000effc6c72b71fcb7125d8b8cd0cc0aa236c1c9ef35b341b59c4c7e973e95014a485199db92a7570470be770ac64bf09e78bb808cf44b53c028c44fe38ef655a7cc4518458761d925a97199fe025f3f97777c8501b591d910997c07c9bda4c1dffc041076c0be6338b3486e6de4c867a2dc34e382d7b5d104931dade89cf4386ae1fb9228c6a5fba598aae82bf5f41a216948a828c769ec44ba4587cdee897a1d22c596b317b557e1fe28e937d8f766154655e442f2428742c2793e421b9afc4189487b48999f654c7421084d31a0c75df75900636d9e1cf335179bd45a8d2d2564ad2fcf9ec010ccc846d410e6d9539217ae2379b2977df16a3392d74504dea932ec8d46dbaea47ab3f1823bc505ee37d48fa23bb5a2f2826b073bf243e23a4a442d206e95017da889c8bbee7a9c77916a2a2f7b0dd0b865308f34f9f03b193be83b1e2da6a565ce513a4da8d8bbe8df5b74293854b97b010c74bdba873c6c660fe0799bd36c0adc3fe3ac24a46686fe24368e80c9dc8743fdd957f7f75fd993dff48f2db25aba6920a7763377ab793de06ef99424fe637958d36e6a284d115ee595bd5986f634171bbd05577f04d974af3bb1a77ac88a70764d7d920a0ef0139c579305ee43fd9e4c3134bf41e51a7b64b998c6a300d99311d9412c5954ecdd642455697fd61052e929ad80429c39449ad0e2867f39f89f5f22733f6ee8d37c10011010001b4425562756e74752041726368697665204175746f6d61746963205369676e696e67204b657920283230313829203c6674706d6173746572407562756e74752e636f6d3e8902380413010a002205025b9fc1da021b03060b090807030206150802090a0b0416020301021e01021780000a0910871920d1991bc93c2c731000a4b6727c73ff959aa0239602b7f983a5076de38281ce43066d210ae1436565afe36eda19e8b708fb8bc340c62c25d977273976a13c9af8cc94e9a600a2a58f5b868374d809b4168d63de32704f65b9058246685c9effe8207b6d6461b75b07ce9b752d367e4980f03b027af10469ec345a665f58e908946deba1ab60d4713a1f55b0716e1adc90de19b5e2ef9befe71bd9bf722a2973ae8bc11764c6a7c9df60b2abed534b955a2090c6ec35b3886f8a6eeeaa08333840d960dcb1fba75e02ad1c406dce25be885182c578790aac21c74592e558e473cf8f62bc4eaa58e924def068746a9ac6d5157c64a6b2dca48ca67c95d5f00a9f87ccf5bca22f3400a2f0b42d9f4c30cb2b012ff8e40bc2dc810a4928632c59f55f57510a23baffb8e6644a19b40a79de191ff12301b22efc85536b06e999c1f21d040d6fdb6f8b638c502bcab85c2a11700f46fa9bf353d6155bb7119c36591a5d2ec0ec3bcfd3e44011792852a3583cf87c293e2baf98b46a68bc629e90605bf08ec403a529bcf82a03f41d234b752013f4374e9141cb357d4680404b73e831b2e73911851e29192667f9d1444fb3dd02310af38cbb05d638b7e5358dc488bc18f417607b2f044bef11a94a920a8bf7a40172ecd75edbbc51da0af99460dec9569d46326545c6121dc7a0859b77f11bc42335be6d7ab7bf62a2beb8e81c5e7cb5525c2d094ce5ad268f8902330410010a001d162104153f1c9ef1395fbf00352e8d0bfb847f3f272f5b05025b9fc443000a09100bfb847f3f272f5b6e170ffd1a069e820bc29f5e50a650016bce8e45e2404719c0c6968bdb6de92e48006c1600393ecf9938f0c070aa19e25918bcc042c18b73a5a44037a07b04023162e9fb5cce1e65011db64fb33dc4efa01cdfcd45017859063f0c2db7323913ac298299f4cff219eacca55c7807c58d6f93feb7db6d030c0047f94db39392de5a55e27930233bf103a5a7ab48162812fff6b73bb0bfaa59e2439d0124ab567f74d05b8085a4b43b6a7885c595d82360e5fec7544df356de2d50ed44ba0e53422442c14668e39bd28db1f3f76660cd9c5ee721346626758d99e6378b235174773091f8245410315daf4705f78512815196c82a1a1dd0014d10f97bfb8813248bd13f729bddd1341b6873d80f10d141d8048c26090c34836257cd9a94f8d862b6ecf99547b8b40881dfaac3f37acf02ed543828d8f73a157669aa64a34519ad05126ebfe5670c17803acb65d10968466e60441a7fc20b7ddc4d4087e409455b8c405ab3d273d9593c1f7066a099212ead688a5fc9f614562488b7f2516d37df94cdf3c67df7e82f43e03248016ef11793fe543300f44f3512e3a409397b516e333418a0125c6303f4b230083b50169a0b8f23528b7e75675e7b13e4960c6c6d8308b1c8fce22f9e946af2ff79e60959e4bf5aabc6cd9cec02d812ba31552ca5b251a462d0dbd85b787f239d13ce3d0f926f06b60bcfd94a805afcbe891a5e510da38b435c8901330410010a001d1621044b96e0121d08b6fc46eb2b0d7de50a8278ddc1f0050261ae911b000a09107de50a8278ddc1f093ea0800a8f6a80eb10e85c67b31c1625c4966cee868bbc802e3d97f53e8f261a6b6c6f5cebd7f2e3d1db064965d905411ff88911ccfab1af5311f62863e9bdcd70ccbb89dedd7ac3dede352109b3f3c7fbb9c4c899a6596ef7a9951d9c5d547e0cdf031f7e6aa1b1e0d26d595c33e119250fe3443675bd629679e2d321e760014eae0b4d368fad55a8bdbfe8995c9ba802f5989b22992dc98213ec963b3d17bfad7f393b0613abeb1c3dc055aa59a09eac5508c8e165bd6196844cd7be61fdd0b0b8534152018ba6d5d720b4472062fc88e94bc391c2db22b71d811a3ba8491b13fb404b7d52444e66bbddb4fef5e580170e0545a338dc450ffa93b30dcca21f86cfd8f Creation Time: Mon Sep 17 15:01:46 UTC 2018 Bit Strength: 4096 Has Revocation: false Has EncryptionKey: true Has MasterKey: true UserId: Ubuntu Archive Automatic Signing Key (2018) <ftpmaster@ubuntu.com>

got that NO_PUBKEY error again tried patching RUN DEBIAN_FRONTEND=noninteractive apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 871920D1991BC93C Into the Dockerfile (not directly but in the script https://github.com/armbian/build/blob/main/lib/functions/host/docker.sh#L276) (^a possible improvement may be: check if the Dockerfile exists, if not then generate it. This may help in cases of Dockerfile experiments, e.g. user edits, but that it is deemed 'do not edit') and run compile.sh again [3/9] RUN DEBIAN_FRONTEND=noninteractive apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 871920D1991BC93C: [🔨] 0.279 Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). [🔨] 0.286 Executing: /tmp/apt-key-gpghome.gobsOrrUwl/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 871920D1991BC93C [🔨] 6.301 gpg: connecting dirmngr at '/tmp/apt-key-gpghome.gobsOrrUwl/S.dirmngr' failed: End of file apparently, keyserver.ubuntu.com is down, does not respond to pings whatever, try again later.

The problem apparently is in the RUN apt-get -y update step in the dockerfile, and it happens during the initial build. It is observed after seperating the apt-get -y update step and the subsequent apt-get install step into 2 RUN commands. For reasons unknown, the same step run in a systemd-nspawn container used for the build works perfectly fine and completes in less than 10 secs. But that it fails while being run in the docker container during the build run by compile.sh turns out there is various network issues in the build docker container driven by compile.sh, need to figure out how to fix that there is no ping and ip command in the image, hence downloaded these using apt-get download iproute2_5.15.0-1ubuntu2_amd64.deb - this is /usr/sbin/ip and friends iputils-ping_3%3a20211215-1_amd64.deb - this is ping and dependencies libcap2-bin_1%3a2.44-1ubuntu0.22.04.1_amd64.deb libmnl0_1.0.4-3build2_amd64.deb libbpf0_1%3a0.5.0-1ubuntu22.04.1_amd64.deb libxtables12_1.8.7-1ubuntu5.1_amd64.de and use docker cp, copy them into the container https://docs.docker.com/engine/reference/commandline/cp/ from there run a shell (/bin/bash) and use dpkg -i to install them all docker run -it [armbian-ubuntu-jammy-latest image ID] /bin/bash root@cee6f1b4e249:/armbian# dpkg -i *deb then docker commit https://docs.docker.com/engine/reference/commandline/commit/ now there is a new image with /usr/sbin/ip and /usr/bin/ping docker network is 'hairy' (lots of pitfalls), edit lib/functions/host/docker.sh https://github.com/armbian/build/blob/main/lib/functions/host/docker.sh#L361 run docker build with --network host, to use the host network to work around some issues in addition use --add-host to work around some DNS issues. well partly as my ipv6 setup is goofed, ipv6 won't route properly in my setup, most likely a cause of the problems.

tried switching the base image to debian-bookworm, unfortunately a same issue appeared after some time during built [🔨] #6 [2/6] RUN echo "--> CACHE MISS IN DOCKERFILE: apt packages." && DEBIAN_FRONTEND=noninteractive apt-get -y update && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends bash git psmisc uuid-runtime bc binfmt-support bison libc6-dev make dpkg-dev gcc ca-certificates ccache cpio debootstrap device-tree-compiler dialog dirmngr dosfstools dwarves flex gawk gnupg gpg imagemagick jq kmod libbison-dev libelf-dev libfdt-dev libfile-fcntllock-perl libmpc-dev libfl-dev liblz4-tool libncurses-dev libssl-dev libusb-1.0-0-dev linux-base locales lsof ncurses-base ncurses-term ntpdate patchutils pkg-config pv qemu-user-static rsync swig u-boot-tools udev uuid-dev zlib1g-dev file tree expect colorized-logs unzip zip pigz xz-utils pbzip2 lzop zstd parted gdisk fdisk aria2 curl wget axel parallel python3-dev python3-distutils python3-setuptools python3-pip gcc-x86-64-linux-gnu gcc-aarch64-linux-gnu gcc-arm-linux-gnueabihf gcc-arm-linux-gnueabi gcc-riscv64-linux-gnu debian-archive-keyring libc6-amd64-cross g++-aarch64-linux-gnu g++ btrfs-progs cryptsetup openssh-client f2fs-tools nilfs-tools xfsprogs zerofree qemu-utils qemu-utils libudev-dev libusb-1.0-0-dev dh-autoreconf build-essential gcc-arm-linux-gnueabi gcc-or1k-elf qemu-utils [🔨] #6 0.996 --> CACHE MISS IN DOCKERFILE: apt packages. [🔨] #6 49.05 Ign:1 http://deb.debian.org/debian bookworm InRelease [🔨] #6 97.10 Ign:2 http://deb.debian.org/debian bookworm-updates InRelease [🔨] #6 145.2 Ign:3 http://deb.debian.org/debian-security bookworm-security InRelease ... [🔨] #6 481.4 Temporary failure resolving 'deb.debian.org' [🔨] #6 529.4 Err:2 http://deb.debian.org/debian bookworm-updates InRelease [🔨] #6 529.4 Temporary failure resolving 'deb.debian.org' [🔨] #6 577.4 Err:3 http://deb.debian.org/debian-security bookworm-security InRelease [🔨] #6 577.4 Temporary failure resolving 'deb.debian.org' [🔨] #6 577.4 Reading package lists... [🔨] #6 577.8 W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease Temporary failure resolving 'deb.debian.org' [🔨] #6 577.8 W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease Temporary failure resolving 'deb.debian.org' [🔨] #6 577.8 W: Failed to fetch http://deb.debian.org/debian-security/dists/bookworm-security/InRelease Temporary failure resolving 'deb.debian.org' [🔨] #6 577.8 W: Some index files failed to download. They have been ignored, or old ones used instead. as i'm not sure how to define that correctly, i patched lib/functions/host/docker.sh docker_cli_prepare() declare -g DOCKER_ARMBIAN_BASE_IMAGE="${DOCKER_ARMBIAN_BASE_IMAGE:-"debian:bookworm"}" # declare -g DOCKER_ARMBIAN_BASE_IMAGE="${DOCKER_ARMBIAN_BASE_IMAGE:-"ubuntu:jammy"}" that managed to pick-up the Debian bookworm image, but the same resolving errors persists

made an attempt to extract /etc/apt/sources.list from the pulled image ghcr.io/armbian/docker-armbian-build, armbian-ubuntu-jammy-latest. replaced that in the Ubuntu Jammy build container /etc/apt/sources.list # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://archive.ubuntu.com/ubuntu/ jammy main restricted # deb-src http://archive.ubuntu.com/ubuntu/ jammy main restricted ## Major bug fix updates produced after the final release of the ## distribution. deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted # deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. deb http://archive.ubuntu.com/ubuntu/ jammy universe # deb-src http://archive.ubuntu.com/ubuntu/ jammy universe deb http://archive.ubuntu.com/ubuntu/ jammy-updates universe # deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb http://archive.ubuntu.com/ubuntu/ jammy multiverse # deb-src http://archive.ubuntu.com/ubuntu/ jammy multiverse deb http://archive.ubuntu.com/ubuntu/ jammy-updates multiverse # deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates multiverse ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse # deb-src http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted # deb-src http://security.ubuntu.com/ubuntu/ jammy-security main restricted deb http://security.ubuntu.com/ubuntu/ jammy-security universe # deb-src http://security.ubuntu.com/ubuntu/ jammy-security universe deb http://security.ubuntu.com/ubuntu/ jammy-security multiverse # deb-src http://security.ubuntu.com/ubuntu/ jammy-security multiverse then sudo apt-get update but that did not resolve the issue, the errors seemed to be always the same hosts and seemingly same specific packages.

For the curious the build is run from within Ubuntu Jammy Jellyfish (22.04) release, running in a systemd-nspwan container, the docker engine is 'outside' the container in the host os. There are lots of issues attempting to run docker engine from within a container. That helps avoid dependency problems for the build as the build environment Ubuntu Jammy 22.04.x amd64 is stated. https://docs.armbian.com/Developer-Guide_Build-Preparation/ The trick is the 'simple' docker.sock method https://devopscube.com/run-docker-in-docker/ i.e. docker client (e.g. compile.sh) runs from within the Ubuntu Jammy Jellyfish container, but setup /var/run/docker.sock so that it can be accessed from within the container by docker client. And outside the container - the host os can run the docker engine (e.g. dockerd, containerd), but sharing out /var/run/docker.sock so that it is the same unix socket accessed by docker client inside the container. Jumped over many hoops, problems to get to this, but the 'network', 'dns resolver' issues remains a bummer. i'm thinking this 'docker in docker' trick may even make it possible to build from within a docker container. e.g. from one docker container use a Ubuntu Jammy Jellyfish (22.04) and run compile.sh . But that pror to that you need to 'remap' the docker.sock so that it can be accessed from the container. e.g. https://devopscube.com/run-docker-in-docker/

While doing the build, I initially ran into various NO_PUBKEY ... error messages accessing security.ubuntu.com, archive.ubuntu.com repositories. e.g. [🔨] 3.570 W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. [🔨] 3.570 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C [🔨] 3.570 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C [🔨] 3.570 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C [🔨] 3.570 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C [🔨] 3.570 W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C it turns out the reply in this post resolves the issue https://askubuntu.com/questions/13065/how-do-i-fix-the-gpg-error-no-pubkey Those using a system installed from the most recent Ubuntu DVD images probably wouldn't hit the issue. But that if you are using an older distribution or that you are trying a build from a distribution other than Ubuntu, this may fix the issue and help 'jump the hoop'.

after quite a few frustrating attempts to setup a built environment, fixing some issues, jumping over some hoops for the build, I managed to get to the 'starting point' of a build ./compile.sh [🌱] uuidgen not found [ uuidgen not installed yet ] [🌱] Using prebuilt Armbian image as base for 'ubuntu-jammy' [ DOCKER_ARMBIAN_BASE_IMAGE: ghcr.io/armbian/docker-armbian-build:armbian-ubuntu-jammy-latest ] [🌿] Docker info [ Docker 19.03.11 Kernel:4.12.14-lp151.28.91-default RAM:31.28GiB CPUs:8 OS:'openSUSE Leap 15.1' hostname 'snoopy1.internal' under 'Linux' - buildx:yes - loop-hacks:yes static-loops:no ] [🌱] Creating [ .dockerignore ] [🌱] Docker launcher [ enabling all extensions looking for Docker dependencies ] [🌱] Extension manager [ processed 27 Extension Methods calls and 82 Extension Method implementations ] [🌱] Adding rootfs encryption related packages [ cryptsetup cryptsetup-initramfs ] [🌱] Preparing rkdevflash host-side dependencies [ rkdevflash ] [🌱] Creating [ Dockerfile; FROM ghcr.io/armbian/docker-armbian-build:armbian-ubuntu-jammy-latest ] [🌱] Armbian docker image [ already exists: ghcr.io/armbian/docker-armbian-build:armbian-ubuntu-jammy-latest ] [🌱] Building [ Dockerfile via 'buildx build --progress=plain --load' ] [🔨] #0 building with "default" instance using docker driver [🔨] [🔨] #1 [internal] load build definition from Dockerfile [🔨] #1 transferring dockerfile: 2.12kB done ... [🔨] #6 [2/6] RUN echo "--> CACHE MISS IN DOCKERFILE: apt packages." && DEBIAN_FRONTEND=noninteractive apt-get -y update && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends bash git psmisc uuid-runtime bc binfmt-support bison libc6-dev make dpkg-dev gcc ca-certificates ccache cpio debootstrap device-tree-compiler dialog dirmngr dosfstools dwarves flex gawk gnupg gpg imagemagick jq kmod libbison-dev libelf-dev libfdt-dev libfile-fcntllock-perl libmpc-dev libfl-dev liblz4-tool libncurses-dev libssl-dev libusb-1.0-0-dev linux-base locales lsof ncurses-base ncurses-term ntpdate patchutils pkg-config pv qemu-user-static rsync swig u-boot-tools udev uuid-dev zlib1g-dev file tree expect colorized-logs unzip zip pigz xz-utils pbzip2 lzop zstd parted gdisk fdisk aria2 curl wget axel parallel python3-dev python3-distutils python3-setuptools python3-pip python2 python2-dev gcc-x86-64-linux-gnu gcc-aarch64-linux-gnu gcc-arm-linux-gnueabihf gcc-arm-linux-gnueabi gcc-riscv64-linux-gnu debian-archive-keyring libc6-amd64-cross g++-aarch64-linux-gnu g++ btrfs-progs cryptsetup openssh-client f2fs-tools nilfs-tools xfsprogs zerofree qemu-utils qemu-utils libudev-dev libusb-1.0-0-dev dh-autoreconf build-essential gcc-arm-linux-gnueabi gcc-or1k-elf qemu-utils [🔨] #6 0.958 --> CACHE MISS IN DOCKERFILE: apt packages. [🔨] #6 49.04 Ign:1 http://archive.ubuntu.com/ubuntu jammy InRelease [🔨] #6 49.04 Ign:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [🔨] #6 97.09 Ign:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease ... [🔨] #6 200.2 Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [🔨] #6 200.2 Temporary failure resolving 'security.ubuntu.com' ... [🔨] #6 481.5 Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease [🔨] #6 481.5 Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 529.5 Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [🔨] #6 529.5 Temporary failure resolving 'archive.ubuntu.com' Is anyone else encountering a similar issue? The builds seemed to be failing repeatedly at DNS resolution to the repositories. Didn't manage to get past this point as the builds failed repeatedly here many minutes to like 1/2 hour and abort, many times with no successes so far. They also seem to be the same few accesses and possibly packages. [🔨] #6 481.4 Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease [🔨] #6 481.4 Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 529.4 Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [🔨] #6 529.4 Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 577.5 Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [🔨] #6 577.5 Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 577.5 Reading package lists... [🔨] #6 578.1 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 578.1 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 578.1 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 578.1 W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease Temporary failure resolving 'security.ubuntu.com' [🔨] #6 578.1 W: Some index files failed to download. They have been ignored, or old ones used instead.

linux-sunxi has a page on Orange Pi zero 3 https://linux-sunxi.org/Xunlong_Orange_Pi_Zero3 quite an informative page about the board

check in this thread there are some *unofficial* images created by others and placed elsewhere (not sure if they are still valid), there are various issues e.g. with wifi not working, issues with boot loader etc discussed in the thread to support the new board would take quite a lot of effort off *everyone* who wants to use the board (development and tests, and contnuous maintenance over long term, kernel updates, distribution updates etc, perpetual) and possibly needs to be funded here. but that orange-pi-zero-3 is an important board first of all that it has up to 4GB memory which is much more than orange-pi-zero-2 so it still matters (a lot) there are some efforts at the "bleeding edge" in the mainline kernels, those are very much 'in development' at the "bleeding edge" and those changes have not been back ported in any way into the existing armbian kernels. https://linux-sunxi.org/Xunlong_Orange_Pi_Zero3

a uwe5622 Wifi problem seem to afflict the Orange Pi Zero 3 as well thoughts are it may take using newer drivers and uwe5622 firmware codes https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-6.1-sun50iw9/drivers/net/wireless/uwe5622 i read somewhere that various works on uwe5622 drivers has been done in the 'upstreamed' recent kernels > 6.5 ? There has been complaints that different vendor's uwe5622 drivers creates a problem as they possibly conflict. Hence, it may help to try find the 'upstreamed' uwe5622 driver implementations and perhaps 'backport' it into the current kernels used in armbian e.g. 6.1.31

for ARM based SOCs, a problem is that there is no 'generic' kernel that can support the specific in chip and on board hardware components e.g. the HDMI graphics drivers, all the various components wifi, ethernet, even on chip interfaces such as usb, memory flash, mmc support and even power management, powering on and off and all that are *distinct* and most of that *undocumented* across ARM SOCs, this is true be they 32 bits or 64 bits. which practically means that searching for an 'OS' that is 'compatible' is going to either simply draw a blank or that you are going to get an 'OS' in which many parts are broken, e.g. no HDMI, no graphics drivers, no usb, no wifi, no ethernet, no nothing etc. you simply have to research the challenges supporting all the different boards here. bitness is a different challenge, for one, using 64 bits vs 32 bits may mean gigabytes of gigabytes / billions of all the apps, shared libraries, kernel, drivers etc would need to be recompiled into 64 or 32 bit binaries. effectively needing 2 universes of binaries to support the whole suite of apps

moderators/admins, I'm thinking it could help to put Orange Pi Zero 3 in its own unmaintained boards sub section, it is likely there'd be more threads related to this and to move this thread and the other thread into the new orange pi zero 3 board section

I'd just like to put a note that for wifi, even the propietary drivers seemed 'unstable', I'm not sure if it is just the drivers itself or something else

hi, just like to join this discussion in a 'development' sense it seemed there are some works in the head Linux v6.5-rc1 https://groups.google.com/g/linux-sunxi/c/p64EM9m9inY https://linux-sunxi.org/Xunlong_Orange_Pi_Zero3 https://linux-sunxi.org/Linux_mainlining_effort they seemed to be continued works on H616 mainlining efforts, but that those are working on H618 e.g. Orange Pi zero 3 etc it could be good to look at the head revisions e.g. v6.5 when we 'backport' codes into e.g. v6.1.31 that is used with armbian. that could save a lot of rework if at some point we (armbian) decide to move on and use a new kernel e.g. v6.5 and accordingly, i read a post that say things like the wifi drivers as different vendors tried to implement their own drivers, it creates a 'problem' for the mainlining efforts to attempt to reconcile 2 different versions of the 'same driver'. Hence, it may be good to look at head revisions e.g. v6.5 while 'porting' them back into v6.1.31. it would likely allow us to have 1 version of drivers e.g. from mainline that possibly works on different boards using the same wifi chips etc.

I've been trying the vendor images (non-armbian, but likely an armbian derivative) https://drive.google.com/drive/folders/1CJYrhHyyje9dEY4-t7JhcZBJfdAFBJro https://drive.google.com/drive/folders/10zlO-0mMz-fqRQOKAOWX-mQA_UbN_C1n and the wifi malfunctioned after running for some 1+ days, things got worse as initially i've been able to manually restart the wifi. then some other corruption creep in on the microsd card and I'm not sure the cause of it. note, non-armbian. for armbian, i think wifi etc is still 'work in progress', wifi isn't quite working yet as of last try, as noted in some earlier comments above.

i think orange pi zero 3 is after all gaining popularity as it is an 'upgraded' orange pi zero 2, 2+ with more dram, e.g. like up to 4 GB, that will make a lot of difference for some apps http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-3.html

there is a new thread open on orange pi zero 3