mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2443] Arm Architecture Build #1716
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#1716
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 @c1rca on GitHub (Dec 2, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2443
It would be great if we could run nginx-proxy-manager:bullseye on arm builds. When I try and build it on oracle's ampere cloud it fails to exec bash.
@stijnos1991 commented on GitHub (Dec 11, 2022):
Yes this would be great. It seems to fail on ARM somehow. I can find additional related issues here on Github. I'm also using Ampere at Oracle.
@Coast47 commented on GitHub (Jan 15, 2023):
Can't run latest nginx proxy manager release (2.19) on arm architecture because it needs rust>=1.48 and latest buster package version is 1.41
error: Rust 1.41.1 does not match extension requirement >=1.48.0 [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for cryptography ERROR: Could not build wheels for cryptography, which is required to install pyproject.toml-based projects@github-actions[bot] commented on GitHub (Feb 3, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 20, 2025):
Issue was closed due to inactivity.