ArchError: Could not find 'cpu MHz' in /proc/cpuinfo

[dmohns]

Description

I'm trying to run a (relatively complex) docker image that somehow uses information from /proc/cpuinfo.

The command that produces the error is /usr/bin/blender --version.

docker context use colima
docker run --rm --platform linux/amd64 ghcr.io/inti-cmnb/kicad7_auto_full:latest /usr/bin/blender --version

Produces

 ArchError: Could not find 'cpu MHz' in /proc/cpuinfo
  Function: Arch_ComputeNanosecondsPerTick
      File: /home/sybren/buildbot-builder/linux_glibc217_x86_64_cmake/build_deps/deps/build/usd/src/external_usd/pxr/base/arch/timing.cpp
      Line: 149

If I run the same using OrbStack everything works

docker context use orbstack
docker run --rm --platform linux/amd64 ghcr.io/inti-cmnb/kicad7_auto_full:latest /usr/bin/blender --version

produces

Blender 3.4.1
	build date: 2022-12-20
	build time: 00:46:45
	build commit date: 2022-12-19
	build commit time: 17:00
	build hash: 55485cb379f7
	build platform: Linux
	build type: release

Version

Colima Version:

colima version 0.5.5
git commit: 6251dc2c2c5d8197c356f0e402ad028945f0e830

runtime: docker
arch: aarch64
client: v24.0.4
server: v20.10.20

Lima Version:

limactl version 0.16.0

Qemu Version:

qemu-img version 8.0.3
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers

Operating System

• [ ] macOS Intel <= 12 (Monterrey)
• [ ] macOS Intel >= 13 (Ventura)
• [ ] macOS M1 <= 12 (Monterrey)
• [X] macOS M1 >= 13 (Ventura)
• [ ] Linux

Output of colima status

INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/d.mohns/.colima/default/docker.sock

Reproduction Steps

1. Run docker run --rm --platform linux/amd64 ghcr.io/inti-cmnb/kicad7_auto_full:latest /usr/bin/blender --version

Expected behaviour

Command should work and output information about Blender.

Additional context

No response

[anthonator]

I think we’re seeing something similar with a Kubernetes workload in a dind situation.

We see:

failed to run Kubelet: could not detect clock speed

[AleMuzzi]

Seems related to https://github.com/docker/for-mac/issues/6047 and https://gitlab.com/qemu-project/qemu/-/issues/750 I'm having the same issue, running bpy 4.0 in a container