Docker Community Forums

Share and learn in the Docker community.

Amd64 Error for silicon M1

Hello, just trying my last chance here

Does anybody ever had this kind of problem?

This is normal. It is just a warning to let you know the performance may be worse, since the architecture is emulated. It happens when the image doesn’t have an ARM version.

Thank you for that, but when I want to get running, ita always in restarting frease.

Check the logs for those containers. The emulation does not always work but the restarting could be caused by something else. The warning itself can be harmless.

goroutine 1 [running]:


-----> Setting PGVERSION=13 PGBIN=/usr/lib/postgresql/13/bin PGCONF_FILE=/etc/postgresql/13/main/postgresql.conf

/usr/local/go/src/runtime/asm_amd64.s:252 fp=0xc420024768 sp=0xc420024760


/usr/local/go/src/runtime/proc.go:127 +0x6c fp=0xc4200247c0 sp=0xc420024768


/usr/local/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc4200247c8 sp=0xc4200247c0

runtime: failed to create new OS thread (have 2 already; errno=22)

fatal error: newosproc

runtime stack:

runtime.throw(0x4cb21f, 0x9)

/usr/local/go/src/runtime/panic.go:566 +0x95

runtime.newosproc(0xc42002a000, 0xc420039fc0)

/usr/local/go/src/runtime/os_linux.go:160 +0x194

runtime.newm(0x4d6db8, 0x0)

/usr/local/go/src/runtime/proc.go:1572 +0x132


/usr/local/go/src/runtime/proc.go:126 +0x36


/usr/local/go/src/runtime/asm_amd64.s:298 +0x79



the fatal error is the same for all the services in my docker-compose.
Any idea what is the reason for this problem?

Since I can’t see the full name of the Docker images can you share the name of at least one of the failing containers? I can try it on my Mac.

In the meantime you can try this postgres which worked on my machine:

docker run -d --name pgtest --platform linux/amd64 postgres:14

Thank you, but did not work :confused:

Where is amd64 version postgres:14? I don’t see that failing. I don’t see that at all.