#geodesic (2024-08)
Discussions related to https://github.com/cloudposse/geodesic
Archive: https://archive.sweetops.com/geodesic/
2024-08-22
v3.2.0 Included Tools
Update Python to 3.12.5, fix init script @Nuru (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”2481971607” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/955“…
2024-08-28
Hello, maybe i’ve missed a step but when trying to run make all for geodesic 2.5.0 or 3.2.0 the upstream repository dl.clousmith.io fails & seems like it could be a misconfig/bug
STEP 14/28: RUN apt-get update && apt-get install -y -u --allow-downgrades terraform-1="${TF_1_VERSION}-*" && update-alternatives --set terraform /usr/share/terraform/1/bin/terraform
Hit:1 <http://deb.debian.org/debian> bookworm InRelease
Get:2 <http://deb.debian.org/debian> bookworm-updates InRelease [55.4 kB]
Get:3 <http://deb.debian.org/debian-security> bookworm-security InRelease [48.0 kB]
Ign:4 <https://dl.cloudsmith.io/public/cloudposse/packages/deb/debian> bookworm InRelease
Get:5 <http://deb.debian.org/debian-security> bookworm-security/main arm64 Packages [176 kB]
Get:6 <https://packages.cloud.google.com/apt> cloud-sdk InRelease [1618 B]
Get:8 <https://packages.cloud.google.com/apt> cloud-sdk/main arm64 Packages [1011 kB]
Hit:7 <https://packages.opentofu.org/opentofu/tofu/any> any InRelease
Get:9 <https://packages.cloud.google.com/apt> cloud-sdk/main all Packages [1511 kB]
Ign:4 <https://dl.cloudsmith.io/public/cloudposse/packages/deb/debian> bookworm InRelease
Ign:4 <https://dl.cloudsmith.io/public/cloudposse/packages/deb/debian> bookworm InRelease
Err:4 <https://dl.cloudsmith.io/public/cloudposse/packages/deb/debian> bookworm InRelease
Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 146.112.250.226 443]
Fetched 2803 kB in 7s (388 kB/s)
Reading package lists...
W: Failed to fetch <https://dl.cloudsmith.io/public/cloudposse/packages/deb/debian/dists/bookworm/InRelease> Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 146.112.250.226 443]
@Jeremy G (Cloud Posse)
@Sean This very unintuitive error happens when your Docker file system runs out of disk space. Try running docker system prune first to free up some space.
100GB free there but critical to know the issue is in fact on my end. Thank you so much for confirming! I’ll dig into it
I’m out-of-office until Tuesday but thought I would leave my findings here:
While investigating the script for the cloudposse package repo I’ve found that when I pull the geodesic base image & run uname -m it returns aarch64 instead of arm64 that is one of the explicit checks
Running as a build layer I got:
STEP 13/30: COPY bash.deb.sh /tmp/bash.deb.sh
--> 6a532fde94d3
STEP 14/30: RUN chmod +x /tmp/bash.deb.sh && /tmp/bash.deb.sh
Executing the setup script for the 'cloudposse/packages' repository ...
OK: Checking for required executable 'curl' ...
OK: Checking for required executable 'apt-get' ...
OK: Detecting your OS distribution and release using system methods ...
^^^^: ... Detected/provided for your OS/distribution, version and architecture:
>>>>:
>>>>: ... distro=debian version=12 codename=bookworm arch=aarch64
>>>>:
OK: Checking for apt dependency 'apt-transport-https' ...
OK: Checking for apt dependency 'ca-certificates' ...
OK: Checking for apt dependency 'gnupg' ...
RUN: Importing 'cloudposse/packages' repository GPG keys ...gpg: no valid OpenPGP data found.
OK: Checking for apt signed-by key support ...
OK: Importing 'cloudposse/packages' repository GPG keys ...
NOPE: Checking if upstream install config is OK ...
^^^^: ... Failed to fetch configuration for your OS distribution release/version.
>>>>:
>>>>: It looks like it might be because the configuration endpoint is not
>>>>: currently available. Please try again in 10-15 minutes. If it still
>>>>: doesn't work after an hour, please contact cloudposse
>>>>: for assistance.
>>>>:
The virtual machine has 100GB free and is pruned (host is ~350GB free) , 5 cpu , & 8GB ram
I have tested with Docker-Desktop & Podman-Desktop (rootless & root). Verified a handful of silly reasons for the docker exit code 100 like LF vs CRLF , can’t find anything off other than the uname -m value consumed by the script that builds the image
@Sean I have to think you have a corrupted build cache or something like that. (Also, I note that when I build Geodesic 3.2.0, Docker reports 35 steps, while your builds have other numbers of steps. Maybe you’ve tinkered with the Dockerfile or something.)
Here’s what I get (note that aarch64 is the correct architecture designator for Debian on ARM64):
⨠ curl -1sLf '<https://dl.cloudsmith.io/public/cloudposse/packages/cfg/setup/bash.deb.sh>' | bash
Executing the setup script for the 'cloudposse/packages' repository ...
OK: Checking for required executable 'curl' ...
OK: Checking for required executable 'apt-get' ...
OK: Detecting your OS distribution and release using system methods ...
^^^^: ... Detected/provided for your OS/distribution, version and architecture:
>>>>:
>>>>: ... distro=debian version=12 codename=bookworm arch=aarch64
>>>>:
OK: Checking for apt dependency 'apt-transport-https' ...
OK: Checking for apt dependency 'ca-certificates' ...
OK: Checking for apt dependency 'gnupg' ...
OK: Checking for apt signed-by key support ...
OK: Importing 'cloudposse/packages' repository GPG keys ...
OK: Checking if upstream install config is OK ...
OK: Installing 'cloudposse/packages' repository via apt ...
OK: Updating apt repository metadata cache ...
OK: The repository has been installed successfully - You're ready to rock!