mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 04:45:48 +03:00
[PR #380] A few changes to the Dockerfile #397
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#397
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?
📋 Pull Request Information
Original PR: https://github.com/acme-dns/acme-dns/pull/380
Author: @nresare
Created: 5/7/2025
Status: 🔄 Open
Base:
master← Head:dockerfile_fix📝 Commits (1)
93c5db7A few changes to the Dockerfile📊 Changes
1 file changed (+10 additions, -11 deletions)
View changed files
📝
Dockerfile(+10 -11)📄 Description
Submitting this as a PR mainly to solicit feedback and discuss potentially contributing documentation on how to best run acme-dns in Kubernetes. Since I wanted to build the docker images for arm64 anyway, I thought I might as well make some other changes:
The last one bit me a little as I tried making some changes to the local repository, only to have
docker buildbuild from the latest master commit, disregarding my local changes.One thing that differs with this docker image compared to the previous one is that as it is set up to run as an unprivileged user, the process does not have permission to open ports under 1024 without special capabilities configuration. In Kubernetes, ports can be remapped via the Service or some Ingress or Gateway implementation, so this is not a problem, but I guess it would require some rewriting of the current docker setup documentation.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.