[GH-ISSUE #584] Feature Request: Docker Hub Multiarch Tag #193

New issue

Open

opened 2026-02-26 04:34:20 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 04:34:20 +03:00

Owner

Originally created by @mageddo on GitHub (Sep 30, 2024).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/584

Summary & Motivation

Docker hub tags named by ${VERSION_NUMBER} or by latest have all possible archs using mutiarch push feature so people can use one specific tag for multiple archs.

Example:

Provide a solver which can solve from previously configured DNS records.
It's will be useful because people can use DPS for static DNS entries instead of use /etc/hosts or something like.

Goals

What is supposed to do in short. (Optional)

Example

A simple, static DNS server

Non-Goals

What people would think it is supposed to do, but it is not? (Optional)

Example

Not to implement a full and complex DNS server

Description

Explain the feature details and how it would work, usecases, examples, snippets of code,
inputs and outputs, etc. (Required)

Example

Storage

DNS records will be stored at the existing DPS config file.

DNS Records

It will have support to A, AAAA and CNAME entries.

Also, TTL by record will be supported

https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/

Originally created by @mageddo on GitHub (Sep 30, 2024). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/584 ## Summary & Motivation Docker hub tags named by ${VERSION_NUMBER} or by latest have all possible archs using mutiarch push feature so people can use one specific tag for multiple archs. Example: > Provide a solver which can solve from previously configured DNS records. > It's will be useful because people can use DPS for static DNS entries instead of use /etc/hosts or something like. ## Goals > What is supposed to do in short. (Optional) Example > A simple, static DNS server ## Non-Goals > What people would think it is supposed to do, but it is not? (Optional) Example > * Not to implement a full and complex DNS server ## Description > Explain the feature details and how it would work, usecases, examples, snippets of code, > inputs and outputs, etc. (Required) Example > ### Storage > > DNS records will be stored at the existing DPS config file. > > ### DNS Records > * It will have support to A, AAAA and CNAME entries. > * Also, TTL by record will be supported ## Related content * https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/