请问有树莓派版本吗

[CrazyBunQnQ]

树莓派官方系统无法启动该镜像

Describe the bug

我在树莓派 4B 官方系统(armv7)上使用您说两种方式都未能成功启动，自行构建也未能成功启动，一直重启

To Reproduce

由于网络问题所以手动下载了这 5 个包

Dockerfile 调整如下:

install.sh 脚本移除了下载包的步骤:

执行的构建命令和运行命令:

docker build -t crazybun/aria2-ui:3.13 .
docker run -itd --name ariang \
  --restart=always \
  -p 80:80 \
  -p 443:443 \
  -e PUID=0 \
  -e PGID=0 \
  -e ENABLE_AUTH=true \
  -e ENABLE_RCLONE=false \
  -e RPC_SECRET=helloworld \
  -e DOMAIN=http://cloud.crazybunqnq.com \
  -e ARIA2_SSL=false \
  -e ARIA2_USER=crazybunqnq \
  -e ARIA2_PWD=rhxrM9UtUWCogQNp \
  -e ARIA2_EXTERNAL_PORT=80 \
  -v /wd/aria2/data:/data \
  -v /wd/aria2/app/a.db:/app/filebrowser.db \
  -v /wd/aria2/sslkeys:/app/conf/key \
  -v /wd/aria2/app/conf:/app/conf \
  crazybun/aria2-ui:3.13

启动容器后一直显示 Restarting (x) 40 seconds ago

Expected behavior

我看您的镜像是支持 armv7 架构的，能帮看下我哪里操作设置不对么...?

[wahyd4]

First of all, this docker image should support ARM chips, I was testing the multi-platform feature by using Mac OSX.

Also, there might be a few potential issues after I read the information you provided:

• If you have running this docker image locally, or you don't have public IP, or you haven't bound your domain to your IP, then you shouldn't use environment variable DOMAIN
• You can try to use the simplest command to run this docker image, which means without persistent volumes to see if it works. You can run the container docker run --rm -it -p 8080:80 wahyd4/aria2-ui:latest, once the container is up and running without errors, try to use http://yourip:8080 to access it, you can also disable rclone if you don't have a stable connection to github by adding -e ENABLE_RCLONE=false
• Lastly, please paste the full container logs to help with debugging.

[CrazyBunQnQ]

Thank you for your reply. I have tried this command "docker run --rm -it -p 8080:80 wahyd4/aria2-ui:latest" as well as previous versions without success.

I have the domain name bound to the IP, but not HTTPS, Does this make a difference?

[wahyd4]

Please attach the logs of the container when you run that simple command. That’s critical information.

About the HTTPS thing, I guess you need to set HTTPS domain to the DOMAIN env.

On Tue, 6 Apr 2021 at 10:59 pm, Baojunjie @.***> wrote:

Thank you for your reply. I have tried this command "docker run --rm -it -p 8080:80 wahyd4/aria2-ui:latest" as well as previous versions without success.

I have the domain name bound to the IP, but not HTTPS, Does this make a difference?

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/wahyd4/aria2-ariang-docker/issues/155#issuecomment-814099672, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGMHYHJ34MFFD3IIO6B4KDTHMASZANCNFSM42OUURRQ .

-- Kind regards, Junwei Zhao

[CrazyBunQnQ]

I see the error log. The configuration cannot be found.

Is this normal?

[wahyd4]

That's fine, the root cause should be the error of aria2c which says 57 segmentation fault.

Can you give it a try with the legacy arm32 tag docker run --rm -it wahyd4/aria2-ui:arm32 to see if it works?

[CrazyBunQnQ]

I tried this command and the results are as follows:

Raspberry Pi 4b is arm32v7 architecture, Is it because of this?

[wahyd4]

Hi @CrazyBunQnQ looks like the CPU complains about the arm32 version program of Caddy. Besides, from the Pi's official website https://www.raspberrypi.org/products/raspberry-pi-4-model-b/specifications/ , the pi 4b has ARMv8 CPU instead of V7.

So please give it a try with docker run --rm -it wahyd4/aria2-ui:arm64 to see how it goes.

[CrazyBunQnQ]

But when I run it, it tells me that it can't run on armv7...

[CrazyBunQnQ]

I used the command to confirm the system architecture:

My Raspberry Pi system is Raspberry Pi OS Lite

[wahyd4]

HI @CrazyBunQnQ, based on all the information we have at this stage, there should be some bug on arm tag docker images, I will try to get a Raspberry Pi to help with debugging arm tags.

If you want to help make it happen sooner, you can think about donating or sponsoring this project.

[CrazyBunQnQ]

Thank you! Expect the perfect ARM tag docker images!

[CrazyBunQnQ]

Hi @wahyd4, The image of my local build reported the following error after startup, do you know how to deal with this?

[wahyd4]

I don't know what's the error is all about, but it seemed the same error as you had when you use my docker image.

By the way, I have tested against the Amazon arm64 server and it worked like a charm. I will try to find some time to test it on Raspberry Pi.

[CrazyBunQnQ]

I didn't solve this problem fundamentally, but it can work normally by installing Ubuntu on the Raspberry Pi, thanks!

[wahyd4]

Hi @CrazyBunQnQ thanks for the update, the behaviour in Pi OS Lite looks really interesting. so it seems not to be a CPU arch issue, instead, it's likely an OS issue. I'd like to keep this open till I test it on a Pi OS Lite.

[CrazyBunQnQ]

Hi @CrazyBunQnQ thanks for the update, the behaviour in Pi OS Lite looks really interesting. so it seems not to be a CPU arch issue, instead, it's likely an OS issue. I'd like to keep this open till I test it on a Pi OS Lite.

Hi @wahyd4 , I found that the official system of the Raspberry Pi has 64-bit. Although it is still being tested, it has been more than a year. I think it should be no problem, but I did not try it because I switched to OMV.