DNS issues when using sysbox-runc in a macvlan
@rodnymolina is already working on this.
Since Sep 23, 2024.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Hey everyone,
thank you for your work on sysbox!
I am running sysbox-runc on archlinux which I know is not officially supported. Still, it would be much appreciated if you could give any pointers.
When I run a container that is connected to a macvlan with sysbox-runc and run e.g. curl example.org in that container, I get a lot of DNS queries even after I get the response from curl. If I use 8.8.8.8 as DNS server via the compose file, everything seems to be working fine. DNS queries go out, request to example.org is made, response is shown, no further DNS queries. However, I am posting this here because if I do not use sysbox-runc, everything works fine without specifying the DNS server in the compose file. I used wireshark for my observations. Any idea what I am missing?
compose file
services:
debug-dns:
build:
context: .
dockerfile: Dockerfile
# I toggled these during my experiments
# runtime: sysbox-runc
# dns: 8.8.8.8
entrypoint: ["tail", "-F", "anything"]
networks:
debug-network:
networks:
debug-network:
external: true
name: my-macvlan-net
Note: This is image dose not require sysbox-runc. I just used it for demonstration purposes. I encountered this while actually using nestybox/ubuntu-noble-systemd-docker
Corresponding Dockerfile
FROM ubuntu
RUN apt update && apt install -y neovim curl
my-mavlan-net:
docker network create -d macvlan --subnet=192.168.2.0/24 --gateway=192.168.2.1 -o parent=eth0 my-macvlan-net
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.