Post "http://host.crc.testing:7777/services/forwarder/expose": dial tcp: lookup host.crc.testing: no such host

[moinessim]

This doesn't work for me. Instead I get this:

$ podman run -dt -p 9999:80 --network bridge alpine_nginx
Error: error configuring network namespace for container 475324f18865edfd5a06a69de07c808f1c68653281fda8975592f92c34a1a832: error adding pod charming_babbage_charming_babbage to CNI network "podman": Post "http://host.crc.testing:7777/services/forwarder/expose": dial tcp: lookup host.crc.testing: no such host

Originally posted by @jrwren in #11396 (comment)

[moinessim]

Getting the same error:

sudo podman run --rm --name nix-docker -p 3022:22 --network bridge lnl7/nix:ssh

Error: error preparing container d108758f5d33b01a222a4c6845aeefa839531e572068194e7dc00bc7d60f09bb for attach: error configuring network namespace for container d108758f5d33b01a222a4c6845aeefa839531e572068194e7dc00bc7d60f09bb: error adding pod nix-docker_nix-docker to CN I network "podman": Post "http://host.crc.testing:7777/services/forwarder/expose": dial tcp: lookup host.crc.testing: no such host

Same error without sudo.

podman info:

host:
  arch: amd64
  buildahVersion: 1.23.1
  cgroupControllers: []
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.30-2.fc35.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.30, commit: '
  cpus: 1
  distribution:
    distribution: fedora
    variant: coreos
    version: "35"
  eventLogger: journald
  hostname: localhost.localdomain
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.14.10-300.fc35.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree: 614465536
  memTotal: 2061529088
  ociRuntime:
    name: crun
    package: crun-1.2-1.fc35.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.2
      commit: 4f6c8e0583c679bfee6a899c05ac6b916022561b
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.12-2.fc35.x86_64
    version: |-
      slirp4netns version 1.1.12
      commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
      libslirp: 4.6.1
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.0
  swapFree: 0
  swapTotal: 0
  uptime: 3h 40m 15.4s (Approximately 0.12 days)
plugins:
  log:
  - k8s-file
  - none
  - journald
  network:
  - bridge
  - macvlan
  volume:
  - local
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
  - quay.io
store:
  configFile: /var/home/core/.config/containers/storage.conf
  containerStore:
    number: 9
    paused: 0
    running: 0
    stopped: 9
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /var/home/core/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 2
  runRoot: /run/user/1000/containers
  volumePath: /var/home/core/.local/share/containers/storage/volumes
version:
  APIVersion: 3.4.0
  Built: 1633030336
  BuiltTime: Thu Sep 30 19:32:16 2021
  GitCommit: ""
  GoVersion: go1.16.8
  OsArch: linux/amd64
  Version: 3.4.0

[Luap99]

Does dns inside the VM work? What is in /etc/resolv.conf?

[moinessim]

Hi @Luap99 ,

I guess DNS is working.
The ping command output is strange though...
And not even my host can resolve host.crc.testing.

[core@localhost ~]$ ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
ping: Warning: time of day goes back (-5022546784433589638us), taking countermeasures
ping: Warning: time of day goes back (-5022546784433585808us), taking countermeasures
64 bytes from 8.8.8.8: icmp_seq=0 ttl=255 time=0.000 ms
wrong data byte #16 should be 0x10 but was 0x0
#16 0 5 0 2 b5 bf 68 61 0 0 0 0 f4 4b d 0 0 0 0 0 10 11 12 13 14 15 16 17 18 19 1a 1b
#48 1c 1d 1e 1f 20 21 22 23

[core@localhost ~]$ ping www.google.com

PING www.google.com (142.250.217.228) 56(84) bytes of data.
64 bytes from 142.250.217.228 (142.250.217.228): icmp_seq=0 ttl=255 time=7678499513187869 ms
wrong data byte #16 should be 0x10 but was 0x0
#16 0 6 0 1 34 c0 68 61 0 0 0 0 95 86 1 0 0 0 0 0 10 11 12 13 14 15 16 17 18 19 1a 1b
#48 1c 1d 1e 1f 20 21 22 23
^Cping: Warning: time of day goes back (-3662127298483108027us), taking countermeasures
ping: Warning: time of day goes back (-3662127298481957502us), taking countermeasures
64 bytes from 142.250.217.228: icmp_seq=0 ttl=255 time=0.000 ms (DUP!)

[core@localhost ~]$ curl -vvv www.google.com > /dev/null

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 142.250.217.228:80...

• Connected to www.google.com (142.250.217.228) port 80 (#0)

GET / HTTP/1.1
Host: www.google.com
User-Agent: curl/7.78.0
Accept: /

• Mark bundle as not supporting multiuse
  < HTTP/1.1 200 OK
  < Date: Fri, 15 Oct 2021 01:47:21 GMT

# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search .

[Luap99]

Does it work after you run podman machine stop and podman machine start again?

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

Since the question was never answered, I am closing the issue, Reopen if you have more data.