Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

add ARM support #28

Open
flowreaction opened this issue Sep 16, 2020 · 1 comment
Open

add ARM support #28

flowreaction opened this issue Sep 16, 2020 · 1 comment

Comments

@flowreaction
Copy link

It would be great if an ARM23/64 image would be available.

@flowreaction
Copy link
Author

I decided to buildon ARM64 myself using the dockerfile provided

staticfloat pushed a commit that referenced this issue Jun 23, 2022
Our parent container is build for multiple architectures, so I think
it would be nice if we followed suite. With this change we will be
able to build the following platforms:

- linux/amd64
- linux/386
- linux/arm64
- linux/arm/v7
- linux/mips64le
- linux/s390x
- linux/ppc64le

However, we will only create a push function for the top 4, since
the bottom 3 takes over 30 minutes to build, and none have asked
for these yet.

Instructions on how to set up Docker Buildx (which is required for
this) can be found in [issue #28][1].

The reason for the "32-bit fix" added to the Dockerfile is a very
interesting read, which can be found in [issue #30][2], but the
TL;DR is that there exist a very exotic bug for some low level
libraries when they try to access the filesystem while running inside
a 32-bit environment that is emulated by QEMU running on a 64-bit host.
For this reason we will need to pin the package version to something
that is not being compiled, but this is ONLY necessary if it is inside
a QEMU emulation.

[1]: JonasAlfredsson/docker-nginx-certbot#28
[2]: JonasAlfredsson/docker-nginx-certbot#30
staticfloat pushed a commit that referenced this issue Jun 23, 2022
This workflow will be triggered when any tag, that match the semi-
regex (it is not normal regex, since "." is treated as a normal
period here), is pushed to the repository. The helper script will
then properly extract the version numbers we are interested in,
before the Docker image is built and tagged properly.

More info about this can be found in issue #28:
JonasAlfredsson/docker-nginx-certbot#28
staticfloat pushed a commit that referenced this issue Jun 23, 2022
This workflow will be triggered when something is changed inside either
the `src/` or the `.github/workflows/` folder on either the "main" or
the "master" branch, all other changes will be ignored. This should
be fine since an edit to the README would not affect how the Docker
container is being built.

More info about this can be found in issue #28:
JonasAlfredsson/docker-nginx-certbot#28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant