support for apple silicon linux/arm64/v8 platform

[vynu]

ran v0.38.6 on Apple Silicon chip, observed error/warning : The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

container status Exited (255)

might need to use docker BuildX for multi platform

NOTE

built new image using Dockerfile with buildx --platform linux/arm64/v8 , container spun up successfully, but hitting UI 8080 showing following error:
failed to get container "/" with error: unable to find data in memory cache

[vynu]

W1214 18:53:39.531179 1 nvidia.go:61] NVIDIA GPU metrics will not be available: no NVIDIA devices found W1214 18:53:39.537655 1 sysinfo.go:203] Nodes topology is not available, providing CPU topology E1214 18:53:39.538209 1 info.go:114] Failed to get system UUID: open /etc/machine-id: no such file or directory W1214 18:53:39.567902 1 container.go:545] Failed to update stats for container "/dhcpcd": open /sys/fs/cgroup/memory/dhcpcd/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.571029 1 container.go:545] Failed to update stats for container "/": open /sys/fs/cgroup/memory/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.579995 1 container.go:545] Failed to update stats for container "/binfmt": open /sys/fs/cgroup/memory/binfmt/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.580167 1 container.go:545] Failed to update stats for container "/006-metadata": open /sys/fs/cgroup/memory/006-metadata/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.580346 1 container.go:545] Failed to update stats for container "/systemreserved": open /sys/fs/cgroup/memory/systemreserved/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.580683 1 container.go:545] Failed to update stats for container "/systemreserved/trim-after-delete": open /sys/fs/cgroup/memory/systemreserved/trim-after-delete/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.581053 1 container.go:545] Failed to update stats for container "/005-dhcpcd": open /sys/fs/cgroup/memory/005-dhcpcd/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.581531 1 container.go:545] Failed to update stats for container "/001-sysctl": open /sys/fs/cgroup/memory/001-sysctl/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.581884 1 container.go:545] Failed to update stats for container "/008-mount-docker": open /sys/fs/cgroup/memory/008-mount-docker/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.582320 1 container.go:545] Failed to update stats for container "/podruntime/docker": open /sys/fs/cgroup/memory/podruntime/docker/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.572262 1 container.go:545] Failed to update stats for container "/docker/f088db6845f63205dba1ea7901173f6a5127c4e875333003d8b2e06622ea5dd3": open /sys/fs/cgroup/memory/docker/f088db6845f63205dba1ea7901173f6a5127c4e875333003d8b2e06622ea5dd3/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.572704 1 container.go:545] Failed to update stats for container "/docker/buildkit": open /sys/fs/cgroup/memory/docker/buildkit/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.573289 1 container.go:545] Failed to update stats for container "/002-format": open /sys/fs/cgroup/memory/002-format/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.574034 1 container.go:545] Failed to update stats for container "/004-mount": open /sys/fs/cgroup/memory/004-mount/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.574468 1 container.go:545] Failed to update stats for container "/000-sysfs": open /sys/fs/cgroup/memory/000-sysfs/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.575158 1 container.go:545] Failed to update stats for container "/systemreserved/diagnose": open /sys/fs/cgroup/memory/systemreserved/diagnose/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.575881 1 container.go:545] Failed to update stats for container "/systemreserved/socks": open /sys/fs/cgroup/memory/systemreserved/socks/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.576419 1 container.go:545] Failed to update stats for container "/systemreserved/acpid": open /sys/fs/cgroup/memory/systemreserved/acpid/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.577438 1 container.go:545] Failed to update stats for container "/systemreserved/ntpd": open /sys/fs/cgroup/memory/systemreserved/ntpd/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.577578 1 container.go:545] Failed to update stats for container "/003-extend": open /sys/fs/cgroup/memory/003-extend/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.578136 1 container.go:545] Failed to update stats for container "/systemreserved/vpnkit-forwarder": open /sys/fs/cgroup/memory/systemreserved/vpnkit-forwarder/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.578787 1 container.go:545] Failed to update stats for container "/podruntime": open /sys/fs/cgroup/memory/podruntime/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.578867 1 container.go:545] Failed to update stats for container "/docker": open /sys/fs/cgroup/memory/docker/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.584113 1 container.go:545] Failed to update stats for container "/kubepods": open /sys/fs/cgroup/memory/kubepods/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.584518 1 container.go:545] Failed to update stats for container "/007-swap": open /sys/fs/cgroup/memory/007-swap/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.585550 1 container.go:545] Failed to update stats for container "/009-bridge": open /sys/fs/cgroup/memory/009-bridge/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:53:39.585959 1 container.go:545] Failed to update stats for container "/kmsg": open /sys/fs/cgroup/memory/kmsg/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.655839 1 container.go:545] Failed to update stats for container "/systemreserved/socks": open /sys/fs/cgroup/memory/systemreserved/socks/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.677104 1 container.go:545] Failed to update stats for container "/binfmt": open /sys/fs/cgroup/memory/binfmt/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.740769 1 container.go:545] Failed to update stats for container "/dhcpcd": open /sys/fs/cgroup/memory/dhcpcd/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.741906 1 container.go:545] Failed to update stats for container "/docker": open /sys/fs/cgroup/memory/docker/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.777069 1 container.go:545] Failed to update stats for container "/008-mount-docker": open /sys/fs/cgroup/memory/008-mount-docker/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.778182 1 container.go:545] Failed to update stats for container "/systemreserved/trim-after-delete": open /sys/fs/cgroup/memory/systemreserved/trim-after-delete/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.853075 1 container.go:545] Failed to update stats for container "/kmsg": open /sys/fs/cgroup/memory/kmsg/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.902839 1 container.go:545] Failed to update stats for container "/003-extend": open /sys/fs/cgroup/memory/003-extend/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.924457 1 container.go:545] Failed to update stats for container "/000-sysfs": open /sys/fs/cgroup/memory/000-sysfs/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:39.972342 1 container.go:545] Failed to update stats for container "/001-sysctl": open /sys/fs/cgroup/memory/001-sysctl/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.046739 1 container.go:545] Failed to update stats for container "/systemreserved/acpid": open /sys/fs/cgroup/memory/systemreserved/acpid/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.078703 1 container.go:545] Failed to update stats for container "/podruntime/docker": open /sys/fs/cgroup/memory/podruntime/docker/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.152564 1 container.go:545] Failed to update stats for container "/kubepods": open /sys/fs/cgroup/memory/kubepods/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.244869 1 container.go:545] Failed to update stats for container "/systemreserved/vpnkit-forwarder": open /sys/fs/cgroup/memory/systemreserved/vpnkit-forwarder/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.244869 1 container.go:545] Failed to update stats for container "/009-bridge": open /sys/fs/cgroup/memory/009-bridge/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.289594 1 container.go:545] Failed to update stats for container "/systemreserved/diagnose": open /sys/fs/cgroup/memory/systemreserved/diagnose/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.416221 1 container.go:545] Failed to update stats for container "/006-metadata": open /sys/fs/cgroup/memory/006-metadata/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.436762 1 container.go:545] Failed to update stats for container "/007-swap": open /sys/fs/cgroup/memory/007-swap/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.513122 1 container.go:545] Failed to update stats for container "/docker/f088db6845f63205dba1ea7901173f6a5127c4e875333003d8b2e06622ea5dd3": open /sys/fs/cgroup/memory/docker/f088db6845f63205dba1ea7901173f6a5127c4e875333003d8b2e06622ea5dd3/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.579669 1 container.go:545] Failed to update stats for container "/systemreserved": open /sys/fs/cgroup/memory/systemreserved/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.734436 1 container.go:545] Failed to update stats for container "/005-dhcpcd": open /sys/fs/cgroup/memory/005-dhcpcd/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.776231 1 container.go:545] Failed to update stats for container "/": open /sys/fs/cgroup/memory/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.784185 1 container.go:545] Failed to update stats for container "/004-mount": open /sys/fs/cgroup/memory/004-mount/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.998697 1 container.go:545] Failed to update stats for container "/002-format": open /sys/fs/cgroup/memory/002-format/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:40.999043 1 container.go:545] Failed to update stats for container "/systemreserved/ntpd": open /sys/fs/cgroup/memory/systemreserved/ntpd/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:41.053612 1 container.go:545] Failed to update stats for container "/podruntime": open /sys/fs/cgroup/memory/podruntime/memory.numa_stat: no such file or directory, continuing to push stats W1214 18:54:41.343179 1 container.go:545] Failed to update stats for container "/docker/buildkit": open /sys/fs/cgroup/memory/docker/buildkit/memory.numa_stat: no such file or directory, continuing to push stats

[cqboyone]

i have the same question too.

[triscuitcircuit]

same error here, except when compiling to wasm with rust lang it causes a seg fault. Cargo also wont exit and the fans turn on full blast and wont stop.

My issue could just be an issue with the rust lang compiler itself however, and only related to this thread by the warning

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

qemu: uncaught target signal 11 (Segmentation fault) - core dumped
error: could not compile rustc-demangle

Caused by:
  process didn't exit successfully: rustc --crate-name rustc_demangle /root/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/rustc-demangle-0.1.18/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=e06072b379804616 -C extra-filename=-e06072b379804616 --out-dir /deploy/target/wasm32-unknown-unknown/release/deps --target wasm32-unknown-unknown -L dependency=/deploy/target/wasm32-unknown-unknown/release/deps -L dependency=/deploy/target/release/deps --cap-lints allow (signal: 11, SIGSEGV: invalid memory reference)
warning: build failed, waiting for other jobs to finish...
thread rustc panicked at invalid terminator state, compiler/rustc_middle/src/mir/mod.rs:1200:34
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: rustc 1.48.0 (7eac88abb 2020-11-16) running on x86_64-unknown-linux-gnu

note: compiler flags: -C opt-level=3 -C embed-bitcode=no --crate-type lib```

[edmondliang]

I have the same problem with M1 as well.
docker run -ti google/cloud-sdk:latest gcloud version

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested Google Cloud SDK 321.0.0 alpha 2020.12.11 app-engine-go 1.9.71 app-engine-java 1.9.84 app-engine-python 1.9.91 app-engine-python-extras 1.9.91 beta 2020.12.11 bigtable bq 2.0.64 cbt 0.9.0 cloud-datastore-emulator 2.1.0 cloud-firestore-emulator 1.11.11 cloud-spanner-emulator 1.1.1 core 2020.12.11 datalab 20190610 gsutil 4.57 pubsub-emulator 0.2.0

[iwankgb]

@edmondliang you are trying to run amd64 Linux build on arm64 Mac OS. This is not expected to work.

[iwankgb]

@triscuitcircuit why do you think your problem is related to cAdvisor?

[triscuitcircuit]

@iwankgb probably not, I am able to view whats going on in the containers without a problem. It seems to be an issue with Qemu or Rustc itself but im not really sure which one.

[iwankgb]

@vynu It seems to me that your problem is another issue (see #2743) related to topology detection on ARM systems. I will try to fix it but I need to have another two PRs merged first.

[vynu]

@iwankgb got it.. could you help me find out exactly where its been failing ?

[iwankgb]

@vynu the problems seems to be located in runc that cAdvisor uses to get information from memory.numa_stat file. I think that this function is a culprit.

Fixing it is a bit complicated, because:

1. One has to fix runc
2. And then update runc version that cAdvisor uses.

[vynu]

aah!! gotcha ...

[nouaman]

This is a docker problem in version 20.
Version 19 should work fine.
see docker/for-linux#1170 (comment)

[iwankgb]

@nouaman yes, it is part of the problem. Another one is that Apple hardware seem not to expose certain files in sysfs.

[iwankgb]

@vynu can you provide me with the following (all from Apple M1 system):

• a snapshot of cgroup filesystem (usually can be found at /sys/fs/cgroup
• a snapshot of /sys/devices/system/cpu directory
• content of /proc/cpuinfo

[xiazemin]

The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "npm start": executable file not found in $PATH: unknown.
ERRO[0001] error waiting for container: context canceled

[kirankumar3054]

I am getting same issue on my M1 MacAir when tried to run a docker image. Any work arounds ?? Appreciate your responses. Thank you!
➜ ~ docker run -d -p 4445:4444 --name selenium-hub selenium/hub
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
24413a6e827abb7da77492369b2503e7b2e1fce4efd403b6b163c99ac8940fb2

[iwankgb]

@vynu @kirankumar3054 can you provide:

• a snapshot of /sys/devices/system/cpu directory
• content of /proc/cpuinfo

Both of the artifacts must be retrieved from Linux VM running on m1 system.

[rubanik00]

@vynu @kirankumar3054 who managed to solve the problem?

[muhammadumairmubasher]

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

I'm using Macbook pro M1! Help Please.....!

[KatyaPrusakova]

Same problem on M1 !

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
WARN: Jupyter Notebook deprecation notice https://github.com/jupyter/docker-stacks#jupyter-notebook-deprecation-notice.

[elubilu]

Having the same issue till now!
Is there any solution for M1?
I have to submit some of my work within next week :/

[khiemnguyen-ffw]

I have same issue on MacBook Pro M1 also.

[anguloteresa]

Hi. I'm using a Macbook Pro M1. Whenever I run this command I get an error:

docker run -d --name MySQLServerTest -e 'ACCEPT_EULA=Y' -p 1433:1433 microsoft/mssql-server-linux

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
ad678cdab2f16b67735ef339ad7df8542877fd058b665a85eae12b4dbde2859b

Any workarounds?

[iwankgb]

Building cadvisor from source will help you all. Package and/or arm Docker image are not available yet.

[IsidoroAros]

I'm having the same issue. But as commented above, the arm image is not available yet for the M1 processors. We should wait for it or run a VM with Windows and use the classis SMSS there.

[SeungWookHan]

Same error for me!

The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
F0510 07:42:44.447442 1 cadvisor.go:146] Failed to create a Container Manager: could not detect clock speed from output: "processor\t: 0\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 fphp asimdhp cpuid dit\nCPU implementer\t: 0x41\nCPU architecture: 8\nCPU variant\t: 0x1\nCPU part\t: 0xd07\nCPU revision\t: 0\n\nprocessor\t: 1\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 fphp asimdhp cpuid dit\nCPU implementer\t: 0x41\nCPU architecture: 8\nCPU variant\t: 0x1\nCPU part\t: 0xd07\nCPU revision\t: 0\n\nprocessor\t: 2\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 fphp asimdhp cpuid dit\nCPU implementer\t: 0x41\nCPU architecture: 8\nCPU variant\t: 0x1\nCPU part\t: 0xd07\nCPU revision\t: 0\n\nprocessor\t: 3\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 fphp asimdhp cpuid dit\nCPU implementer\t: 0x41\nCPU architecture: 8\nCPU variant\t: 0x1\nCPU part\t: 0xd07\nCPU revision\t: 0\n\nprocessor\t: 4\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 fphp asimdhp cpuid dit\nCPU implementer\t: 0x41\nCPU architecture: 8\nCPU variant\t: 0x1\nCPU part\t: 0xd07\nCPU revision\t: 0\n\nprocessor\t: 5\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 fphp asimdhp cpuid dit\nCPU implementer\t: 0x41\nCPU architecture: 8\nCPU variant\t: 0x1\nCPU part\t: 0xd07\nCPU revision\t: 0\n\n"

Any workarounds?

[Y2Data]

Guys, did add "--platform linux/amd64" fix your problem?

[tianzihao]

same problem 😩

[deathdefyer]

+1

[LeeeeeeM]

is there any solution?

[emevieira123]

https://debugsolutions.wordpress.com/2021/03/17/using-sql-server-on-m1-based-mac-with-docker/

Vlw funcionou pra mim também

[simplenotezy]

@Y2Data Tried running a legacy project inside Docker. Got same error. With the --platform linux/amd64 flag, I get a new error instead.

❯ docker run --name php -v web:/var/www/html -d tommylau/php-5.2 --platform linux/amd64
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
54343f4708869e7e2c90a3f85d10bd868d753dddcb00abe6da983a31e83ef653
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "--platform": executable file not found in $PATH: unknown.

[martadinata666]

is m1 mac cant use normal arm64 image?
my pi4 ubuntu use this man image https://hub.docker.com/r/zcube/cadvisor

[Dinidu]

+1

[sacsand]

+1

[jufantozzi]

Hi all, Just want to add a brief side note here. If you go to the Docker official docs, you will see that indeed, as @Y2Data said, adding --platform linux/amd64 to your command should fix the problem.

However, the location where you add the command also matters. If you still encounter the same issue, try changing the location of the new command inside your original command.

Thanks @Ianyliu. I was placing the --platform flag on the end of the docker build command and it was failing. Moving it as the first flag in the command solved.

[HyunTaek5]

Same error on M1 pro! Are there any solutions for this issue?

cadvisor_1 | F0506 15:47:20.575673 1 cadvisor.go:175] Failed to create a manager: could not detect clock speed from output: "processor\t: 0\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp flagm2 frint\nCPU implementer\t: 0x00\nCPU architecture: 8\nCPU variant\t: 0x0\nCPU part\t: 0x000\nCPU revision\t: 0\n\nprocessor\t: 1\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp flagm2 frint\nCPU implementer\t: 0x00\nCPU architecture: 8\nCPU variant\t: 0x0\nCPU part\t: 0x000\nCPU revision\t: 0\n\nprocessor\t: 2\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp flagm2 frint\nCPU implementer\t: 0x00\nCPU architecture: 8\nCPU variant\t: 0x0\nCPU part\t: 0x000\nCPU revision\t: 0\n\nprocessor\t: 3\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp flagm2 frint\nCPU implementer\t: 0x00\nCPU architecture: 8\nCPU variant\t: 0x0\nCPU part\t: 0x000\nCPU revision\t: 0\n\nprocessor\t: 4\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp flagm2 frint\nCPU implementer\t: 0x00\nCPU architecture: 8\nCPU variant\t: 0x0\nCPU part\t: 0x000\nCPU revision\t: 0\n\nprocessor\t: 5\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp flagm2 frint\nCPU implementer\t: 0x00\nCPU architecture: 8\nCPU variant\t: 0x0\nCPU part\t: 0x000\nCPU revision\t: 0\n\n"

[ajeetbpr]

When building a docker image on apple M1, i used the --platform option: i.e. docker build -t imagename --platform linux/x86_64 .

Works for me!

thank you so much

[ngannguyen2294]

cadvisor_1 | F0506 15:47:20.575673 1 cadvisor.go:175] Failed to create a manager: could not detect clock speed from output: "...

+1
I am also facing this issue with Mac Pro M1

[ilpianista]

Did I get it right that v.044.1-test provides arm64 support?

[ngannguyen2294]

Did I get it right that v.044.1-test provides arm64 support?

This works for me, Mac Pro M1, macOS Monterey 12.4

[spkane]

Yes. Something like docker run --volume=/:/rootfs:ro --volume=/var/run:/var/run:ro --volume=/sys:/sys:ro --volume=/var/lib/docker/:/var/lib/docker:ro --volume=/dev/disk/:/dev/disk:ro --publish=8080:8080 --detach=true --name=cadvisor --privileged --device=/dev/kmsg gcr.io/cadvisor/cadvisor:v0.44.1-test is working for me on an Arm64 based system.

[sktkddn777]

docker pull zcube/cadvisor
it works on Mac :)

[SayebRahemanIbm]

does above link solved this issue ?

[bobbypage]

Fixed in #3141 (cAdvisor v0.45.0 now has a multi arch image).

[muhammedbasilsk]

@spkane it worked. Thanks a lot :-)

[khaledalam]

Add export DOCKER_DEFAULT_PLATFORM=linux/amd64 before run docker-compose up or any other build commands!

[rnag]

Thanks @khaledalam - adding the export silenced the warnings in my case.

I was additionally passing --platform=linux/amd64 in docker build steps, but one thing I realized is that I was running other docker commands such as docker create and docker cp, so the export option was little better for me, rather than setting --platform explicitly in each command 👍 .

[danilo-garduce]

I'm having same error message running:

docker run -t mcr.microsoft.com/mssql/server:2022-latest --platform linux/x86_64 -d --name sql_server_test -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=xxxxxxxxxxxxxx' -p 1433:1433

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
/opt/mssql/bin/permissions_check.sh: line 4: [: : integer expression expected
/opt/mssql/bin/permissions_check.sh: line 59: [: : integer expression expected
SQL Server 2022 will run as non-root by default.
This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
/opt/mssql/bin/permissions_check.sh: line 68: exec: --: invalid option
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]

[MetaverseMan]

I have same issue on MacBook Pro M1 also.

is this resolved now?

[maitrungduc1410]

I'm using v0.47.2, it's working fine:

version: "3.8"
services:
  cadvisor:
    image: gcr.io/cadvisor/cadvisor:v0.47.2
    ports:
    - 8080:8080
    privileged: true
    devices:
      - /dev/kmsg
    volumes:
    - /:/rootfs:ro
    - /var/run:/var/run:ro
    - /sys:/sys:ro
    - /var/lib/docker/:/var/lib/docker:ro
    - /dev/disk/:/dev/disk:ro
    - /var/run/docker.sock:/var/run/docker.sock:ro
    - /etc/machine-id:/etc/machine-id:ro
    - /var/lib/dbus/machine-id:/var/lib/dbus/machine-id:ro

[Adeniyilowee]

I had the same problem with Cadvisor and the below configuration worked for me:

cadvisor:
 image: gcr.io/cadvisor/cadvisor:v0.47.2
 volumes:
   - /:/rootfs:ro
   - /var/run:/var/run:rw
   - /sys:/sys:ro
   - /var/lib/docker/:/var/lib/docker:ro
 ports:
   - 8080:8080