Closed schmierlappe closed 6 months ago
I'm not sure, this looks more like a general Docker Swarm problem, are you able to run the container using plain docker on the node to see potential problems?
with local docker compose file I get this
[+] Running 0/1 ⠏ autokuma Pulling 0.9s no matching manifest for linux/arm64/v8 in the manifest list entries
tried on a rpi4
Yes I currently don't provide arm images, you would need to build the image from source in that case and arm support is untested
Small update, I just built a aarch64 image locally and everything seems to work fine, that said I won't be able to provide official builds unless/until GitHub rolls out aarch64 to everyone.
could be docker hub an alternative?
there I found this one
yeah, arm64 is very important, we have whole infrastructure on arm (ampere)
I've added qemu based aarch64 builds, unfortunately this increases build time from ~7 minutes to ~60 so I'll only build these on tags. Additionally they will remain experimental for the time being. There is a test build available here: https://github.com/BigBoot/AutoKuma/pkgs/container/autokuma/215277216?tag=sha-1b4bdf8
Thank you, only for major releases will be enough I think)
yes, it could be base image related, try with different distros - debian slim, alpine, etc. I have similar behavior on my project (python, ssl related things...), it depends on build process for dependencies, os related deps, etc.
I'm facing this issue on a rpi's docker swarm config with standard compose file
Error grabbing logs: rpc error: code = Unknown desc = warning: incomplete log stream. some logs could not be retrieved for the following reasons: task ph9yvojkg89sv7g45ugpjdad1 has not been scheduled
any idea?