Skip to content

DNS broken for Linux Sandbox when using systemd-resolved stub resolver #5027

Closed
microsoft/mxc
#1453

Description

@kien-truong

Describe the bug

Currently, when running sandbox in a Linux host with systemd-resolvd stub resolver, the sandbox shares the host's /etc/resolv.conf, which sends DNS to nameserver 127.0.0.53.

However, this address is not reachable from inside the sandbox, as it's a loopback address from the host. This behaviour leads to broken DNS resolution from inside the sandbox.

Affected version

GitHub Copilot CLI 1.0.90

Steps to reproduce the behavior

On a machine which use systemd-resolved stub DNS resolver

  1. Run copilot
  2. Ask it to send a test request to any address, e.g: example.com

Expected behavior

DNS should work with sandbox in Linux box using systemd-resolved stub resolver

Additional context

No response

Activity

  1. added theissue type on Oct 1, 2026
  2. added
    area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictions
    area:platform-linuxLinux-specific: Wayland, X11, Ubuntu, Fedora, Alpine, ARM, terminal emulators
    and removed on Oct 3, 2026
  3. caarlos0 commented on Oct 22, 2026

    @caarlos0
    Member

    Hi, this should be fixed on 1.0.100+.

    Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictionsarea:platform-linuxLinux-specific: Wayland, X11, Ubuntu, Fedora, Alpine, ARM, terminal emulators

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions