Server:
Engine:
Version: 18.09.7
API version: 1.39 (minimum version 1.12)
Go version: go1.10.1
Git commit: 2d0083d
Built: Wed Aug 14 19:41:23 2019
OS/Arch: linux/arm64
Experimental: false
Thanks!
p.s. not sure what’s wrong with formatting, but it doesn’t cooperate with me.
Hi, I’m having a problem related to this: I’m running a docker container and, if I don’t specify the platform manually it’s getting arm build instead of arm64. I wouldn’t care if the arm build worked but it doesn’t, the arm64 does.
To bypass this issue I have to use the --platform option, but this requires the docker server to be set to experimental and I’d rather avoid it.
Is there another way to tell docker to pull arm64 images?
I wish this was mentioned on wiki (coreelec:docker [CoreELEC Wiki]). Have run into this issue recently: scanimage terminates with segmentation fault (#15039) · Issues · alpine / aports · GitLab
TL;DR; for alpine(-based) images make sure you put aarch64 insto /etc/apk/arch before pulling anything from repositories (i. e. apk add ..)
noticed that, I opted to use linuxserver.io from dockerhub using tags :arm64v8version
I am looking to potentially work around it… oddly running 64bit is supported…
CONTAINER ID NAME > CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
20945feb5979 code-server 0.00% 0B / 0B 0.00% 0B / 0B 0B / 0B 0
t-CoreELEC:~ # docker inspect linuxserver/code-server:arm64v8-4.16.1 | grep Architecture
“Architecture”: “arm64”,
t-CoreELEC:~ # docker inspect portainer/portainer-ce | grep Architecture
“Architecture”: “arm”,
is the docker compiled for 64??? and its just the configs that haven’t be adapted to use the os to determine what image to select? instead hardcoded for 32bit?
volumes:
- /storage/.config/dockers/medusa/config:/config
- /var/media/LIXO/COMPLETOS:/downloads
- /var/media/NAS1/Seriados:/tv
- /var/media/NAS1:/NAS1
- /var/media/LIXO:/LIXO
ports:
- 8081:8081
restart: unless-stopped
displays the following error message:
failed to deploy a stack: medusa Pulling no matching manifest for linux/arm/v8 in the manifest list entries
Hi, I think there is a simple workaround/solution, you just have to specify the platform in your compose file, I’m using it like this and it’s working great:
version: '3.9'
services:
pihole:
platform: linux/arm64
image: pihole/pihole:latest
The platform tag may not be available with old versions of docker compose but you can update it by using the binaries provided here: Releases · docker/compose · GitHub
I can even provide a script to automatically update it (using crontab), feel free to use it:
#!/usr/bin/bash
installVersion=$(/storage/.local/bin/docker-compose version | awk '{print $4}')
currentVersion=$(curl -s "https://api.github.com/repos/docker/compose/releases/latest" | /opt/bin/jq -r '.name')
echo installVersion: $installVersion
echo currentVersion: $currentVersion
if [ "$installVersion" != "$currentVersion" ]
echo "update found"
# echo $currentVersion > /storage/.local/bin/compose.version
wget "https://github.com/docker/compose/releases/download/$currentVersion/docker-compose-linux-aarch64" -O /storage/.local/bin/docker-compose.new
if [ "$?" != "0" ]
/storage/telegram.sh N2 "N2+ Docker compose update - WGET ERROR"
mv /storage/.local/bin/docker-compose /storage/.local/bin/docker-compose.old
chmod +x /storage/.local/bin/docker-compose.new
mv /storage/.local/bin/docker-compose.new /storage/.local/bin/docker-compose
/storage/telegram.sh N2 "N2+ Docker compose updated to $currentVersion"
elif [ "$currentVersion" == "null" ]
/storage/telegram.sh N2 "N2+ Docker compose update - CURL ERROR"
