mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #73] ARMHF: node binary damaged #72
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#72
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 @axute on GitHub (Feb 18, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/73
i can not start the docker image on raspi B+ (rev 1.2)
tried following
running with docker version 18.06.1 (other are damaged in raspbian stretch)
@jc21 commented on GitHub (Feb 18, 2019):
Hmm interesting. Will take a look.
@jc21 commented on GitHub (Feb 19, 2019):
Can you give me the following outputs from your Pi console:
uname -acat /proc/cpuinfo | grep Revision@axute commented on GitHub (Feb 19, 2019):
@jc21 commented on GitHub (Feb 19, 2019):
Yeah so you're using a 5 year old Pi and the
armhfdocker image is for thearmv7linstruction set. Honestly, I'm not even sure that the b+ can handle running this docker stack and a database :/@axute commented on GitHub (Feb 19, 2019):
hm okay, yesterday before starting the container, i installed the mariadb-server (per apt on host OS) and created an user with database for nginx-proxy-app.
At the moment i have a nginx-proxy-server running (native, not in docker), also letsencrypt certbot ...
but your UI is much better then my scripts ;-)
where can i find your base-image for the armhf build? i will try to build an armv6 build ;-)
@jc21 commented on GitHub (Feb 20, 2019):
Cool so you'll have to build 2 docker images, one is the base for the other one. I've just added the dockerfiles for
armv6to the repos but as I can't build them, I can't guarantee they'll work :)To build the base:
To build the app:
Let me know how you go!
@hmehra commented on GitHub (Oct 19, 2021):
Unable to build with this error -
`
Architecture: ARM v6
OS: Debian Bullseye
Variant: run variant
Default variable(s): UDEV=off
Extra features:
install_packages <package-name>commandbalena-idlecommandbalena-infocommandGet:1 http://archive.raspberrypi.org/debian bullseye InRelease [23.5 kB]
Get:2 http://archive.raspbian.org/raspbian bullseye InRelease [15.0 kB]
Err:1 http://archive.raspberrypi.org/debian bullseye InRelease
At least one invalid signature was encountered.
Err:2 http://archive.raspbian.org/raspbian bullseye InRelease
At least one invalid signature was encountered.
Reading package lists...
W: GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: At least one invalid signature was encountered.
E: The repository 'http://archive.raspberrypi.org/debian bullseye InRelease' is not signed.
W: GPG error: http://archive.raspbian.org/raspbian bullseye InRelease: At least one invalid signature was encountered.
E: The repository 'http://archive.raspbian.org/raspbian bullseye InRelease' is not signed.
The command '/bin/sh -c apt-get update' returned a non-zero code: 100
`