Giters
containers
/
dnsname
name resolution for containers
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
177
Watchers:
6
Issues:
43
Forks:
49
containers/dnsname Issues
Dependency Dashboard
Updated
6 months ago
Option to customize dnsmasq config
Updated
7 months ago
Comments count
1
'exit status 3' when starting container
Closed
a year ago
Comments count
17
Need this plugin for an offline system
Updated
a year ago
README_PODMAN.md out of date
Updated
a year ago
Comments count
1
Problem when containers resolve each other by name
Updated
a year ago
Comments count
2
Provide possibility to all upstream dns lookups in generated dnsmasq.conf
Updated
a year ago
install: cannot stat 'bin/dnsname': No such file or directory
Updated
2 years ago
Comments count
3
Bug: massiv latency impact when using dnsname (workaround in comment 3)
Closed
3 years ago
Comments count
13
Implicit assumption that dnsmasq is on-host
Updated
2 years ago
Comments count
4
IP addresses aren't removed from addnhosts when using podman-compose
Updated
2 years ago
Comments count
3
make validate fails with No such file or directory
Closed
2 years ago
Comments count
1
Only one container from a pod ends up in addnhosts
Closed
2 years ago
Comments count
1
Can't install: "install: cannot stat 'bin/dnsname': No such file or directory"
Closed
2 years ago
Comments count
2
Installation dnsname /podman on wsl2 : Could not resolve host
Closed
2 years ago
Comments count
1
unexpected behavior when a container is attached to more than one network
Updated
2 years ago
Comments count
4
1.4.0-dev (41c9f66b68968988f4eec21c220a6dba19497596) - error with symlinked /etc/resolv.conf
Updated
2 years ago
dns is not updated when addnhosts change
Updated
2 years ago
Comments count
7
dnsname does not resolve hostnames of containers
Updated
3 years ago
Comments count
6
README_PODMAN.md - recommended apparmor_parser commands cause security issues
Closed
3 years ago
Comments count
1
Listen at 127.0.0.11 (docker compatibility, nginx)
Updated
3 years ago
Comments count
2
What is the correct way to terminate the dnsmasq process?
Closed
3 years ago
Comments count
11
Not able to stop or restart the containers present in same network after dnsname plugin installation
Closed
3 years ago
Comments count
7
Rename master branch to the main branch.
Closed
3 years ago
Comments count
2
Using dnsname plugin with ovs-cni Results in "Temporary failure in name resolution"
Updated
3 years ago
GitHub releases
Updated
3 years ago
Run tests without root privileges
Updated
3 years ago
dns not working when recreate network
Closed
3 years ago
Comments count
16
Using dnsname plugin in rootful podman
Closed
3 years ago
Comments count
2
dnsmasq process in wrong cgroup
Updated
3 years ago
Comments count
5
dnsname - persistent entries in /run/containers/cni/dnsname/podman/addnhosts
Closed
3 years ago
Comments count
17
The --internal flag in podman network create disables dns names
Closed
3 years ago
Comments count
1
README_PODMAN.md: "http://web" is a typo of "http://web.dns.podman" ?
Closed
3 years ago
Comments count
4
dnsname - plugin should be in /usr/libexec/cni
Closed
3 years ago
Comments count
5
Please, correct README_PODMAN.md
Closed
3 years ago
Comments count
2
Option --network-alias still not working
Closed
4 years ago
Comments count
4
How to set up name resolution for pods?
Closed
4 years ago
Comments count
3
disable 'issue creation' in github and describe expected process to use 'bugzilla.redhat.com' in readme.md
Closed
4 years ago
doc uses wrong packagename
Closed
4 years ago
Comments count
1
hostname points to the name of the infra container instead to hostname of the pod itself
Closed
4 years ago
Comments count
9
containers do not start after reboot while dnsname enabled
Updated
4 years ago
Comments count
7
Question: DNS not working as expected
Closed
4 years ago
Comments count
7
podman --subuidname does not set resolv.conf
Updated
5 years ago
Comments count
10