[{"_1":2,"_184":-5,"_185":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_159":160},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":21,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_98":-5,"_99":100,"_148":-5,"_149":11,"_150":21,"_151":11,"_152":-5,"_153":11,"_154":-5,"_155":156,"_157":101,"_158":-7},"canonicalUrl","https://hub.docker.com/r/0xnoid/dockerresolve/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","0xnoid","reponame","dockerresolve","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_53":54,"_56":57,"_58":59,"_60":11,"_61":62,"_63":64,"_65":66,"_43":35,"_32":33,"_68":69,"_70":55,"_71":72,"_73":74,"_75":76,"_77":-5,"_78":72,"_79":80,"_81":11,"_82":33,"_83":84,"_89":11,"_90":91,"_95":33,"_96":97},"categories",[42,47,50],{"_43":44,"_45":46},"name","Networking","slug","networking",{"_43":48,"_45":49},"Security","security",{"_43":51,"_45":52},"Developer tools","developer-tools","content_types",[55],"image","date_registered","2026-01-13T13:35:51.104525Z","description","microDNS allowing host (and host-mode network containers) to resolve Docker containers easily","is_private","last_updated","2026-02-06T12:53:43.337479Z","last_modified","2026-02-06T11:58:52.630202Z","media_types",[67],"application/vnd.oci.image.index.v1+json","pull_count",1138,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# DockerResolve: Minimalistic DNS for Docker\n\nMake sure to star this on [GitHub](https://github.com/0xnoid/DockerResolve) if you enjoy it, or simply want to see what's going on behind the scenes.\n\n---\n> What is DockerResolve?\n\nDockerResolve is a an extremely lightweight, minimalistic and low-configuration DNS server for Docker containers. Allowing DNS resolution on Host for Docker Containers.\n\n

Why?

\n\nBecause there are often situations where you may require to resolve containers by container name/hostname rather than IP. This can be extremely tedious to do.\\\nLet's use an example:\\\nYou have an NGINX container that requires `NETWORK_MODE: HOST`, or, simply, an NGINX server running as a package on your server. While this NGINX server can freely communicate with the containers utilizing the Docker network/s - the internal Docker DNS does not allow DNS queries from anything that isn't directly attached to the specific network.\\\nIn this scenario, that means our NGINX that's host network attached. Which makes it more tedious, because while we CAN contact our internal Docker DNS at `127.0.0.11` you won't get a response.\n\nHowever, when we use DockerResolve, we can now set up this container which hooks straight into the Docker API and creates it's own DNS microservice. Now, we can simply set `resolver {container_ip} valid=30s;` and suddenly we have functioning Docker DNS, allowing us to use important configurations such as `$upstream_app myapp` for our `proxy_pass`.\n

\n\n

How does it work?

\n\nDockerResolve works by attaching straight to the Docker API. Due to this, it's a deliberate choice to make it as nitpicky and limited as possible as not to pose other risks.\\\nWe grab the information by using a standard series of commands integrated. These can be narrowed down to, essentially:\n- `GET /containers/json`: Container overview\n- `GET /containers/{id}/json`: Specific container information\n- `GET /networks`: Network overiew\n- `GET /networks/{id}`: Specific networks\nInn essence, the workflow is very simple.\\\nIntialization:\n1. Get all containers\n2. Filter blacklisted containers\n3. Cache all IPs\n4. Deliver\n\nOnce initialized:\n1. Monitor Docker Events for two things: Network changes / Container state changes. This allows two things: Detect when a container is deleted / restarted / started / created, which can all change the ID, IP or name. It's then matched with the network changes; disconnect, connect.\n2. Upon changes, the Container information is replaced\n3. When a request for a container name is made to the DNS, it's matched towards the corresponding IP, just as Docker's internal DNS would function\n4. Return is given\nIt's important to note that:\n1. The optins you're running with will impact resolvability\n2. IPv6 and IPv4 is a delibarete choice you'll have to make in your networks\n\nThe DNS will often refuse IPv6 requests if the containers are IPv4.\\\nBecause of this, amongst other things, it is HIGHLY recommended to use IPv4 only, and for any queries for containers that these requests are made in IPv4 only. As the response will be a failure.\n\n

\n\n## Configuration\nThis solution is made with simplicity first. There are therefore a few recommendations:\n- Create a specific network for DockerResolve\n- Assign a static IP\nCertain other parts are optional, you'll find all the options for the container below:\n```yaml\nservices:\n dockerresolve:\n image: dockerresolvedns:latest\n container_name: dockerresolve-dns\n environment:\n - CACHE_TIME=10m\n - LOG_LEVEL=2\n - PREFIX=\n - POSTFIX=\n - OUTPUT_DIR=/DockerResolve\n - CUSTOM_HOSTS=\n - BLACKLIST_CONTAINERS=dockerresolve-dns\n - NAME_INTELLIMATCH=false\n - DNS_PORT=53\n volumes:\n - /var/run/docker.sock:/var/run/docker.sock\n```\nFor this configuration, you may pick any. The only requirements are:\n- An IP (so the DNS can receive contact)\n- `/var/run/docker.sock` for using the Docker API.\nTo see the exact details expand the `Environment Options`:\n\n

Environment Options

\n \n- `CACHE_TIME` Cache time for DNS. Coincidentally, this also allows you to choose resource use as the list of Container items grow, as it also specifies our lifetime of the Docker system events.\n- `LOG_LEVEL` Logging level, where 0 is disabled, 1 is base, 2 is default. For the full amount select 5.\n- `PREFIX`: Prefix for DNS. For example, `docker` would mean the DNS resolution will be `docker.nginx` instead of `nginx`\n- `POSTFIX`: Same as `PREFIX` but in the opposite style: `nginx.docker`\n- `OUTPUT_DIR`: Hosts file output directory\n- `CUSTOM_HOSTS`: Internal hosts, only really used for hosts file. For example, if you're using the hosts file and want to keep the original hosts file items such as `127.0.0.1` instead of overwriting the existing one.\n- `BLACKLIST_CONTAINERS`: The blacklist. Items you don't want the DNS to monitor or resolve. For example, if `nginx` is running `NETWORK_MODE: HOST` there's no reason to resolve it or monitor it. adding `nginx` would stop this.\n- `NAME_INTELLIMATCH`: Easier name matching with a bit of leeway. Allows you to not use full name of the container. For example; Trying to resolve `nginx` when the container name is `nginx-web` allows this to do so.\n- `DNS_PORT`: The port. Optional, I suppose.\n- Volumes: `/var/run/docker.sock` is required. If you want to use hosts file I also suggest passing the `/DockerResolve` folder, where you'll find this file.\n\n

\n\nFor an optimal Docker Compose, assign a network and IP:\n\n```yaml\nservices:\n dockerresolve:\n image: dockerresolvedns:latest\n container_name: dockerresolve-dns\n environment:\n - CACHE_TIME=10m\n - LOG_LEVEL=2\n - OUTPUT_DIR=/DockerResolve\n - BLACKLIST_CONTAINERS=dockerresolve-dns\n - NAME_INTELLIMATCH=false\n - DNS_PORT=53\n volumes:\n - /var/run/docker.sock:/var/run/docker.sock\n - ./DockerResolveDNS:/DockerResolve\n restart: unless-stopped\n networks:\n dockerresolvedns:\n ipv4_address: 10.99.99.5\nnetworks:\n dockerresolvedns:\n name: dockerresolvedns\n internal: true\n driver: bridge\n driver_opts:\n com.docker.network.bridge.name: dckr_resolvdns\n ipam:\n config:\n - subnet: 10.99.99.0/24\n```\n\n\n## Other\n#### Security\nThe biggest concern is that the DockerResolveDNS will, inherently, only work with the Docker API and internal services (on the same machine, within host) that are able to use `localhost`. Therefore, you should not for any reason, open any ports, as it does not need it anyway.\\\nThere are few other concerns due to the nature of the server.\n","has_starred","hub_user","immutable_tags_settings",{"_85":11,"_86":87},"enabled","rules",[88],".*","is_automated","permissions",{"_92":21,"_93":11,"_94":11},"read","write","admin","user","storage_size",25939407,"orgData","recentTags",[101],{"_102":55,"_103":104,"_105":106,"_107":108,"_109":110,"_111":112,"_61":136,"_137":104,"_138":33,"_139":67,"_43":140,"_141":142,"_143":144,"_145":136,"_146":76,"_147":21},"content_type","creator",39093717,"digest","sha256:dcdcc5de2c50e274d5579d8cc7261ceb2213fc9f8a55a29474eacff60cd9b164","full_size",7636216,"id",1068403863,"images",[113,129],{"_114":115,"_105":116,"_117":118,"_119":120,"_121":122,"_123":124,"_125":118,"_126":-5,"_127":108,"_73":76,"_128":-5},"architecture","amd64","sha256:414adf585b9ca5175507c9d864490549d49200ba6bb43df98366a30a8675fab5","features","","last_pulled","2026-10-09T18:11:17.802520082Z","last_pushed","2026-02-06T12:53:41.325153675Z","os","linux","os_features","os_version","size","variant",{"_114":130,"_105":131,"_117":118,"_119":132,"_121":133,"_123":130,"_125":118,"_126":-5,"_127":134,"_73":135,"_128":-5},"unknown","sha256:f52fcdb5efab89c43c4340fda7db23a40886bdf9069467b78a7d4071958920ff","2026-08-27T08:54:32.454844095Z","2026-02-06T12:53:41.307798631Z",1331,"inactive","2026-02-06T12:53:42.184039Z","last_updater","last_updater_username","media_type","latest","repository",29741518,"tag_last_pulled","2026-10-11T03:06:43.105269406Z","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":161,"_171":172,"_155":182,"_183":11},{"_40":162,"_53":166,"_56":57,"_58":59,"_60":11,"_61":62,"_63":64,"_65":167,"_43":35,"_32":33,"_68":69,"_70":55,"_71":72,"_73":74,"_75":76,"_77":-5,"_78":72,"_79":80,"_81":11,"_82":33,"_83":168,"_89":11,"_90":170,"_95":33,"_96":97},[163,164,165],{"_43":44,"_45":46},{"_43":48,"_45":49},{"_43":51,"_45":52},[55],[67],{"_85":11,"_86":169},[88],{"_92":21,"_93":11,"_94":11},"tags",{"_173":74,"_174":-5,"_175":-5,"_176":177},"count","next","previous","results",[178],{"_102":55,"_103":104,"_105":106,"_107":108,"_109":110,"_111":179,"_61":136,"_137":104,"_138":33,"_139":67,"_43":140,"_141":142,"_143":144,"_145":136,"_146":76,"_147":21},[180,181],{"_114":115,"_105":116,"_117":118,"_119":120,"_121":122,"_123":124,"_125":118,"_126":-5,"_127":108,"_73":76,"_128":-5},{"_114":130,"_105":131,"_117":118,"_119":132,"_121":133,"_123":130,"_125":118,"_126":-5,"_127":134,"_73":135,"_128":-5},[],"canDeleteTags","actionData","errors"]

0xnoid/dockerresolve

Tags for 0xnoid/dockerresolve