-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Container doesn't work #1
Comments
Hi, the default architecture for docker container was ARM x64, now i've switched it to Intel x86_64 and committed changes, the new image is already built and pushed with support for x86_64 also. Update your downloaded repository with |
Hi, thank you for the quick response. Unfortunately it still doesn't work with the same error. I'm runnning docker on a raspi 4. Mosquitto and HA are running on the same pi. br |
Well, the images are built only for x86_64 and aarch64 architectures. For ARM x64 you should run
Make sure you replaced |
Does this still work? I get error "Unable to query nbe for this time..." |
Hi, make sure you have compatible NBE model. |
I have NBE BS+ (Blackstar+) 16
…On Tue, Oct 31, 2023 at 7:23 AM e1z0 ***@***.***> wrote:
Hi, make sure you have compatible NBE model.
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYBYGO32GKDXGRSKQEXPL3YCCDNXAVCNFSM6AAAAAATQ3WBYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBWGQ3DQNRXGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
My BS+ says, controller version 16.0000.319 |
For me i had to put (debug: "true" ) then it worked for me |
Hi,
first, thanks for sharing your project.
I tried ro install it for getting some information of my nbw pheonix pellet burner.
After starting the docker container i recieve the following log:
standard_init_linux.go:219: exec user process caused: exec format error
My docker compose looks like this
TRUE for debug didn't work, so i replaced it with 1.
Any ideas what causes the problem?
br from germany,
Steffen
The text was updated successfully, but these errors were encountered: