mirror of
https://github.com/bakito/adguardhome-sync.git
synced 2026-03-02 22:57:06 -05:00
Container error code 139 then restarts #104
Labels
No labels
Stale
bug
bug
dependencies
dependency to upstream
duplicate
enhancement
help wanted
missing Information
openapi_gen
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/adguardhome-sync#104
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Martin-Dolan on GitHub (Jul 22, 2024).
What happened?
Installed many times, many different ways, it seems that the container does not even start properly as there is nothing in the logs.
I am running on Pi-os , latest boobworm version with all the updates on raspberry pi 5
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
Tried deploying by command line with docker, and by using portainer.. same thing. just exits with error 139 , no output.
I also made a new container with portainer using the hello-world example, that worked, had something in the log files, so I know the system works enough to deploy a container..
also adguardhome is running fine on this system in another container
AdguardHome-Sync Version
v 0.6.11
(fresh off site as of 23/07/24)
AdguardHome Version
Version: v0.107.51
but its not even getting that far to even try and connect.
Configuration
Current Applied Configuration
Relevant log output
Anything else?
I wish I had a log file to paste here.. then i'd have something to work with..
Thinking the code just does not run on this version of raspberry pi OS
cat /etc/os-releasegives:
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"@bakito commented on GitHub (Jul 23, 2024):
Hi @Martin-Dolan
Are you running the binary or docker version?
Can you please provide the cpu arch of your pi?
uname -m@Martin-Dolan commented on GitHub (Jul 23, 2024):
The raspberry pi 5 is a 64-bit 2.4 GHz quad-core ARM Cortex-A76
I know people have successfully run it on raspberry pi 3 (different chip though)
I'm running the docker version.
I've tried installing it using both methods using Docker CLI and docker compose - (ghcr.io/bakito/adguardhome-sync)
@bakito commented on GitHub (Jul 23, 2024):
what us the output of
uname -m@Martin-Dolan commented on GitHub (Jul 23, 2024):
aarch64
@bakito commented on GitHub (Jul 23, 2024):
There are currently no images available for this arch.
I'll have to add them to the build.
@Martin-Dolan commented on GitHub (Jul 23, 2024):
Ahh ok.. That makes sense.
It's the first time I've tried to set this up, and also the first time I've used docker, portainer and a pi 5 so I want sure if it was because it didn't work /wasn't supported or because I was doing something wrong /stupid/uneducated 🤣
That's why gave it a good go before bothering you!
Also learnt a hell of a lot over the last week and a bit..
Let me know when you want me to test it!
@bakito commented on GitHub (Jul 23, 2024):
@Martin-Dolan can you please try the most recent
maintag image?https://github.com/bakito/adguardhome-sync/pkgs/container/adguardhome-sync
@Martin-Dolan commented on GitHub (Jul 23, 2024):
Still nothing :(
I used
ghcr.io/bakito/adguardhome-sync:mainversion: "2.1" services: adguardhome-sync: image: ghcr.io/bakito/adguardhome-sync:main container_name: adguardhome-sync command: run --config /config/adguardhome-sync.yaml volumes: - /DATA/AppData/adguardhome-sync/config/adguardhome-sync.yaml:/config/adguardhome-sync.yamlAlso tried the same with
ghcr.io/bakito/adguardhome-sync:alpine-mainso is it downloading the right version for my system?
Let me know if I'm doing something stupid...
@bakito commented on GitHub (Jul 24, 2024):
Actially I`m a bit puzzled on which arch is really needed, as I can not test it myself.
Can you give this image a try?
quay.io/bakito/adguardhome-syncDo you have other docker images/applications that run?
If so, can you run
docker inspect <image-name>And do the same with adguardhome sync?
docker inspect ghcr.io/bakito/adguardhome-sync:mainAnd attach the output?
I'm specially intrested in the Architecture an OS sections.
@Martin-Dolan commented on GitHub (Jul 24, 2024):
No problem, I'll do it as soon as I get home.
You know more about this than I do, but as far as I can work out from what I've read, the pi 5 uses arm64 aarch64
This might help?
https://www.raspberrypi.com/documentation/computers/linux_kernel.html
Also if I open a shell from casa os I get :
Linux raspberrypi 6.6.31+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-2 9) aarch64
@Martin-Dolan commented on GitHub (Jul 24, 2024):
Holly sh!t I think you fixed it.
I just ran the docker hello world example again and that said arm64v8
I then noticed you put some more arch versions up and one was arm64v8, so I downloaded adguardhome-sync again and it actually ran this time - well it has something in the log files at least which is a start! ill go and test it actually works now, but at least its running!!
thank you sooooooo much!!!!
@bakito commented on GitHub (Jul 24, 2024):
Good to hear, I'll close the isseu then.
@Martin-Dolan commented on GitHub (Jul 24, 2024):
Yes, just been testing- It's just various config/settings stuff I have to work out now, but it did the symc of 5 pages of static leases which is good!
Thanks again <3
@bakito commented on GitHub (Jul 24, 2024):
a new release is currently being built