Latest image is not pulled , I suggest to wait next build and then inspect
点赞 评论 复制链接分享私信 访问主页
Mmm sorry it s not running anymore :/
But I checked the sha-256 of the image started, and it was not the sha-256 of any image on Docker hub (couldn t find which image it was on Docker hub)
点赞 评论 复制链接分享私信 访问主页
it pulled the wrong image, not in the right architecture.
Can you docker inspect pulled image please ?
I will install your image for testing
点赞 评论 复制链接分享私信 访问主页
Ok, let me explain. I did on my Raspberry Pi v1 (ARMv6)
docker pull gladysassistant/gladys:v4
And it didn t work, it pulled the wrong image, not in the right architecture.
I guess it s because it can t choose with the manifest and picked the amd64 one by default.
Maybe I misunderstood what the manifest does?
点赞 评论 复制链接分享私信 访问主页
I didn t use the gladysassistant/gladys:v4 without -arm because the manifest part is still an experimental feature and I don t want to enable experimental features on a prod environnement.
Maybe I misunderstood but the command docker manifest is experimental , not the builded/tagged image
gladys:v4 gladys:v4-arm , in 2 cases you are using manifest , this is not the tag that define arch but the annotate command.
https://github.com/GladysAssistant/Gladys/blob/master/.circleci/config.yml#L165
To illustrate i can easily use this command to annotate the manifestdocker manifest annotate $DOCKERHUB_REPO:$CIRCLE_TAG $DOCKERHUB_REPO:$CIRCLE_TAG-amd64 --os linux --arch arm --variant v6;
amd64 tag for arm arch
In your example , with the gladysassistant/gladys:v4-arm tag , manifest is still checked because it exist ( via docker run )
点赞 评论 复制链接分享私信 访问主页
Image Raspbian built with all new parameters (expand filesystem, new docker run, unattended upgrade)
The command I used to start gladys is:
docker run -d \\--log-opt max-size 10m \\--restart always \\--privileged \\--network host \\--name gladys \\-e NODE_ENV production \\-e SERVER_PORT 80 \\-e TZ Europe/Paris \\-e SQLITE_FILE_PATH /var/lib/gladysassistant/gladys-production.db \\-v /var/run/docker.sock:/var/run/docker.sock \\-v /var/lib/gladysassistant:/var/lib/gladysassistant \\-v /dev:/dev \\gladysassistant/gladys:v4-arm
I didn t use the gladysassistant/gladys:v4 without -arm because the manifest part is still an experimental feature and I don t want to enable experimental features on a prod environnement.
You can download the image here: https://github.com/GladysAssistant/Gladys/releases/download/v4.0.0-beta.15/gladys-v4-rev1.img.zip
Let me know if you have feedbacks :)
点赞 评论 复制链接分享 提交 再想想 采纳 点击登录 提问题 欢迎建议意见 . 如何写高质量提问和回答? 采纳榜7天 被采纳次数本文链接: http://rcdistribution.immuno-online.com/view-737402.html