codieplusplus/duckdb - Docker Image

AArch64 cpu core information table

AArch64 cpu core information table

Milk-V Titan – A $329 octa-core 64-bit RISC-V mini-ITX motherboard with a PCIe Gen4 x16 slot

We first noted the UltraRISC UR-DP1000-powered Milk-V Titan mini-ITX motherboard when we wrote an article about three high-performance RISC-V processors to watch in H2 2025. There have been some delays, as there often are, but the Titan board finally appears to be in stock, so it's probably a good time to have a closer look. Powered by a 2 GHz UR-DP1000 octa-core RISC-V CPU, the Titan mini-ITX motherboard supports up to 64GB DIMM memory and M.2 NVMe storage (PCIe Gen4 x4), and features a PCIe Gen4 x16 slot for a graphics card or other expansion, Gigabit Ethernet, four USB 3.0 ports, a BMC, and more. Milk-V Titan specifications: CPU - UltraRISC UR-DP1000 8x 64-bit RISC-V UR-CP100 “RV64GCBHX” cores up to 2.0 GHz Two 4x core cluster design with 4MB L3 cache each, and a total of 16MB cache. Fully RVA22 compliant, and “Compliant with RVA23 excluding V extension.” Supports Hardware

LicheePi Console 4A - Sipeed Wiki

BuildKit for RISC-V64: When Your Package Works But Your Container Doesn’t | Bruno Verachten

I shipped BuildKit for RISC-V64 two days ago. The workflows were green, packages built successfully, documentation looked thorough. Then users tried to actually use it. The container crash-looped immediately. "No worker found." Turns out "successful compilation" and "functional deployment" are very different things. The problems: - Missing runc binary meant OCI worker couldn't initialize (BuildKit needs at least one worker to run) - ENTRYPOINT/CMD split was wrong, so Docker Buildx was unable to pass runtime arguments - CI tests hung indefinitely when buildkitd tried to initialize workers without proper privileges - Cached GHCR credentials caused false "access denied" errors Three PRs later, the container works. But here's what I learned: - Testing individual components isn't enough. You need to test how components integrate with the systems that actually use them. It's not enough to verify the car starts; you need to verify it drives. - Always add timeouts. Even commands that "should never hang" will eventually hang. - Use your own packages consistently. Mixing Debian's runc 1.1.12 with our runc 1.3.0 builds created unnecessary version complexity. - Document the WHY, not just the WHAT. Explain when to use container images vs. APT packages. Users need context, not just instructions. The iceberg metaphor fits perfectly: visible success hiding more profound integration problems. Post-deployment debugging is where the real work happens. #BuildKit #RISCV64 #Docker #DevOps #Debugging #ContainerTechnology #LessonsLearned #PostDeployment #devEco

Armbian 25.11 release is coming

Armbian 25.11 code freeze begins November 20th. Maintainers should test boards, resolve critical issues, and join the coordination meeting on November 8th.