Docker problem Temporary failure resolving 'deb.debian.org'

jofen · Jul 5th 2021

Hi,

Using OMV5

Trying to setup wyzecam-bridge docker.

When running composer get this error.

Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/

Building wyzecam-bridge

Sending build context to Docker daemon 17.92kB

Step 1/8 : FROM python:3.9-slim

---> c2f204720fdd

Step 2/8 : RUN apt-get update && apt-get install ffmpeg unzip g++ -y && rm -rf /var/lib/apt/lists/*

---> Running in 1d5000af3b8b

Err:1 http://deb.debian.org/debian buster InRelease

Temporary failure resolving 'deb.debian.org'

Err:2 http://security.debian.org/debian-security buster/updates InRelease

Temporary failure resolving 'security.debian.org'

Err:3 http://deb.debian.org/debian buster-updates InRelease

Temporary failure resolving 'deb.debian.org'

Reading package lists...

W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Temporary failure resolving 'deb.debian.org'

W: Failed to fetch http://security.debian.org/deb…/buster/updates/InRelease Temporary failure resolving 'security.debian.org'

W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Temporary failure resolving 'deb.debian.org'

W: Some index files failed to download. They have been ignored, or old ones used instead.

Reading package lists...

Building dependency tree...

Reading state information...

E: Unable to locate package ffmpeg

E: Unable to locate package unzip

The command '/bin/sh -c apt-get update && apt-get install ffmpeg unzip g++ -y && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

ERROR: Service 'wyzecam-bridge' failed to build

How can i solve the

Err:1 http://deb.debian.org/debian buster InRelease

Temporary failure resolving 'deb.debian.org'

Thanks

macom · Jul 5th 2021

DNS issue. If you are not able to ping deb.debian.org add an additional DNS server in the network settings

jofen · Jul 5th 2021

Thanks macom , but here is configuration.

macom · Jul 5th 2021

Post the output of these commands using the </> code box for each of them.

ping -c 4 8.8.8.8

ping -c 4 google.com

cat /etc/resolv.conf

ls -al /etc/resolv.conf

systemctl status systemd-resolved.service

jofen · Jul 5th 2021

Here is the results.

Running in terminal OMV5.

Thanks

Code

ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=17.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=114 time=17.0 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=114 time=16.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=114 time=17.0 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 7ms
rtt min/avg/max/mdev = 16.916/16.992/17.049/0.139 ms

Code

ping -c 4 google.com
PING google.com (172.217.19.78) 56(84) bytes of data.
64 bytes from ham02s17-in-f14.1e100.net (172.217.19.78): icmp_seq=1 ttl=116 time=24.0 ms
64 bytes from ham02s17-in-f14.1e100.net (172.217.19.78): icmp_seq=2 ttl=116 time=24.0 ms
64 bytes from ham02s17-in-f14.1e100.net (172.217.19.78): icmp_seq=3 ttl=116 time=24.0 ms
64 bytes from ham02s17-in-f14.1e100.net (172.217.19.78): icmp_seq=4 ttl=116 time=23.9 ms

--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 6ms
rtt min/avg/max/mdev = 23.901/23.992/24.041/0.164 ms

Code

cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must 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 192.168.0.175
nameserver 1.1.1.1
nameserver 8.8.8.8

Display More

Code

ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 32 Mar 20 09:55 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

Code

systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d
           └─resolvconf.conf
   Active: active (running) since Sat 2021-06-19 08:59:56 CEST; 2 weeks 2 days ago
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 Main PID: 502 (systemd-resolve)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 3.8M
   CGroup: /system.slice/systemd-resolved.service
           └─502 /lib/systemd/systemd-resolved

Jun 19 08:59:55 openmediavaultL systemd[1]: Starting Network Name Resolution...
Jun 19 08:59:56 openmediavaultL systemd-resolved[502]: Positive Trust Anchors:
Jun 19 08:59:56 openmediavaultL systemd-resolved[502]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Jun 19 08:59:56 openmediavaultL systemd-resolved[502]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jun 19 08:59:56 openmediavaultL systemd-resolved[502]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.a
Jun 19 08:59:56 openmediavaultL systemd-resolved[502]: Using system hostname 'openmediavaultL'.
Jun 19 08:59:56 openmediavaultL systemd[1]: Started Network Name Resolution.

Display More

macom · Jul 6th 2021

Everything looks fine. DNS is working. google.com can be resolved.

Quote from jofen

Temporary failure resolving 'deb.debian.org'

Maybe you just needed to wait a bit. Is it working now?

jofen · Jul 6th 2021

Quote from macom

Everything looks fine. DNS is working. google.com can be resolved.
Maybe you just needed to wait a bit. Is it working now?

Thanks for checking.

No I m not able to run this docker container.

Have other that just run fine.

Once more thanks fort taking your time Macom.

Docker problem Temporary failure resolving 'deb.debian.org'

Participate now!

Similar Threads

NO Dns with Docker Host Network