I have a Rails application that I want to deploy using Docker on an Ubuntu server. I have the Dockerfile for the application already set up, right now I want to view the nginx conf in its container.
I ran the command below to start an nginx container in an interactive mode:
docker run -i -t nginx:latest /bin/bash
Right now I am trying to install nano editor in order to view the configuration for nginx configuration (nginx.conf) using the commands below:
apt-get update
apt-get install nano
export TERM=xterm
However, when I run the first command apt-get update, I get the error below:
Err:1 http://security.debian.org/debian-security buster/updates InRelease
Temporary failure resolving 'security.debian.org'
Err:2 http://deb.debian.org/debian buster InRelease
Temporary failure resolving 'deb.debian.org'
Err:3 http://deb.debian.org/debian buster-updates InRelease
Temporary failure resolving 'deb.debian.org'
Reading package lists... Done
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/debian-security/dists/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.
I have checked very well it has nothing to do with network connectivity. I would need some help. Thank you.
asked May 2, 2020 at 22:58
Promise PrestonPromise Preston
24.5k12 gold badges146 silver badges144 bronze badges
1
Try restarting Docker.
One of these should work:
sudo service docker restart
sudo /etc/init.d/docker restart
sudo snap restart docker
Even in cases where Docker never worked before, some commenters said this was helpful. However, you may have a different issue.
answered Sep 24, 2020 at 20:14
5
Perhaps the network on the VM is not communicating with the default network created by docker during the build (bridge), so try «host» network :
docker build --network host -t [image_name]
for docker-compose:
service_name:
container_name: name
build:
context: .
network: host
answered Mar 19, 2021 at 20:00
manumazumanumazu
8015 silver badges3 bronze badges
11
If you have VPN running, stop it and try again. It solved for me!
answered Aug 14, 2020 at 15:26
1
Run this command:
echo -e «nameserver 8.8.8.8\nnameserver 8.8.4.4» |sudo tee -a /etc/resolv.conf
After that run-
sudo apt-get update
This worked for me.
answered May 20, 2022 at 6:30
1
Here’s how I solved it:
Start the docker container for the application in an interactive mode, in my case it an nginx container :
docker run -i -t nginx:latest /bin/bash
Run the command below to grant read permission to the others role for the resolv.conf file:
chmod o+r /etc/resolv.conf
Note: If you are having this issue on your host machine (Ubuntu Linux OS) and not for the Docker containers, then run the same command adding sudo to it in the host machine terminal:
sudo chmod o+r /etc/resolv.conf
Endeavour to exit your bash interactive terminal once you run this:
exit
And then open a new bash interactive terminal and run the commands again:
apt-get update
apt-get install nano
export TERM=xterm
Everything should work fine now.
Reference to this on Digital Ocean: Apt error: Temporary failure resolving ‘deb.debian.org’
That’s all.
Asclepius
58.2k17 gold badges167 silver badges144 bronze badges
answered May 2, 2020 at 22:58
Promise PrestonPromise Preston
24.5k12 gold badges146 silver badges144 bronze badges
1
sudo vi /etc/docker/daemon.json
and check flag of iptables, aslo add DNS if not added
{...., "iptables":true,"dns": ["8.8.8.8", "8.8.4.4"]}
then
sudo service docker restart
solved me
answered Apr 14, 2022 at 10:23
Victor OrletchiVictor Orletchi
4691 gold badge5 silver badges15 bronze badges
0
I had the same problem and in my case it was file access control.
I uses extended acls on the docker root folder and did not realize it, because they where inherited from the folder above (stupid idea to test docker in a «scratch» directory where permissions are set via extended acls).
This lead to the situation that «/etc/resolv.conf» had setting «640» inside the running docker container with a «+» marking the extended acls. But the image did not have extended acls installed and could not handle it.
The weird thing was that, as far as I can see, all other network tools worked (e.g. ping) but only apt could no access the DNS resolver.
After removing the extended acls from the docker root and setting the usual acls, everything worked inside the running container.
Similar to the answer of «Promise Prestion», but solved permanently for new containers, too.
answered Mar 25, 2021 at 14:50
MarcoMarco
8249 silver badges13 bronze badges
1
Under Debian, as root, I’ve ran:
/etc/init.d/docker restart
This solved the issue for me.
Then build and run the container again.
sɐunıɔןɐqɐp
3,34215 gold badges36 silver badges40 bronze badges
answered Jan 27, 2021 at 19:17
0
I easily resolved it via:
- docker exec -it nginx bash (Go inside container)
- ping google.com (if not working)
- exit (Exit from container)
- sudo service docker restart
Please also confirms /etc/sysctl.conf
- net.ipv4.ip_forward = 1
sudo sysctl -p /etc/sysctl.conf
answered May 3, 2020 at 4:57
I was having the wrong DNS IP address in my /etc/docker/daemon.json. In my case, it was my home router DNS IP address and I was trying from the office network.
I found out my office DNS and updated with that.
{
"dns": ["192.168.1.1"]
}
Eric Aya
69.5k35 gold badges181 silver badges253 bronze badges
answered Jun 29, 2022 at 17:59
1
I had a similar issue, I tried many suggested solutions, but my issue was gone after I rebooted my VM.
Asclepius
58.2k17 gold badges167 silver badges144 bronze badges
answered Sep 2, 2020 at 14:30
babis21babis21
1,5351 gold badge16 silver badges30 bronze badges
Similar issue, under debian.
Root cause was a bad DOCKER-USER rule in iptables chain
Those rules have been haded
iptables -I DOCKER-USER -i eno1 -j DROP
iptables -I DOCKER-USER -s 90.62.xxx.xx/32 -i eno1 -j ACCEPT
so removing temporarily following rule fix the point
iptables -D DOCKER-USER -i eno1 -j DROP
answered Jul 15, 2021 at 13:35
Coming here from some docker cross compiling headache:
While forking some repo I manually downloaded its root folder containing confd stuff and added it just like the original maintainer did.
ADD root /
after this I was not able to apt update anymore.
I found that the permission of my root named folder was wrong. stat -f "%OLp" root revealed it is 700, but must be 755 to work.
answered Oct 9, 2021 at 22:02
MaxMax
5022 gold badges4 silver badges14 bronze badges
I’m using Arch version 6.0.11 and docker version 20.10.21, and having this issues inside docker containers.
Thanks to @Marco, that was the initial hint to solve this. The problem is related to the use of extended ACLs in the host system.
The docker root folder has ACLs, you can see this as it has a plus sign at the end of permissions «+»:
$ sudo ls -lh /var/lib/docker
drw-rw-r--+ 3 root root 4.0K Nov 24 2021 network
And what is the problem? Some docker images does not have ACLs installed, so as it was pointed this causes an issue.
Other network tools like curl resolved DNS properly, but apt or git have problems with DNS resolution.
TLDR; Where is the fix? Modify ACL to set default rx to others.
setfacl -R -d -m o::rx /var/lib/docker
After that, all network tools will be able to perform DNS resolution.
Credits:
Marco comment
Closed git issue in docker
Antoine
1,3934 gold badges20 silver badges26 bronze badges
answered Dec 11, 2022 at 18:55
The answer from @Mario Olivio Flores suggests using the service command. That is correct and probably works currently on all Linux distributions. However, as most Linux distributions prefer systemd over systemV, it seems better to use just that with the following command:
sudo systemctl restart docker
For example, on my Linux distribution the service script located at /usr/sbin/service just wraps systemctl, see this excerpt:
# When this machine is running systemd, standard service calls are turned into
# systemctl calls.
if [ -n "$is_systemd" ]
then
UNIT="${SERVICE%.sh}.service"
case "${ACTION}" in
restart|status|try-restart)
exec systemctl $sctl_args ${ACTION} ${UNIT}
;;
answered Feb 27 at 12:06
For me, it turned out to be a random WSL 2 issue — running wsl --shutdown and restarting the containers solved it for me.
answered Mar 27 at 14:22
It used to work before, then I got the same error. I’ve had a Debian and a Docker update in the meantime however. And I’ve found, that the latest Docker on debian/bookworm has this /etc/docker/daemon.json config:
{
"bridge": "none"
}
Changing "none" to "" followed by the command systemctl docker restart solved my problem. Seems like it uses the default bridge that I have had before, you may have to create it.
answered Aug 10 at 21:33
Self-Hosted Version
22.8.0
CPU Architecture
x86_64
Docker Version
20.10.17
Docker Compose Version
2.6.0
Steps to Reproduce
mkdir -p /root/sentry
cd /root/sentry
rm -fr self-hosted
git clone https://github.com/getsentry/self-hosted.git
cd self-hosted
MY_NETWORK="my-overlay-network"
cat << EOF >> docker-compose.yml
networks:
default:
external: true
name: ${MY_NETWORK}
EOF
sed -i "s/\${COMPOSE_PROJECT_NAME}_default/${MY_NETWORK}/g" ./install/wrap-up.sh
./install.sh --skip-user-prompt
In the above, I’m specifying a network as per #1302.
EDIT this issue seems to be unrelated to the use of a custom network as per above steps. I get the same failure resolving 'deb.debian.org' errors with a very basic install:
mkdir -p /root/sentry
cd /root/sentry
rm -fr self-hosted
git clone https://github.com/getsentry/self-hosted.git
cd self-hosted
./install.sh
Expected Result
No errors. It has worked up till now, though admittedly I haven’t tried for a couple of months so various dependencies may have been updated since then.
Actual Result
▶ Parsing command line ...
▶ Detecting Docker platform
Detected Docker platform is linux/amd64
▶ Initializing Docker Compose ...
▶ Setting up error handling ...
▶ Checking for latest commit ...
▶ Checking minimum requirements ...
Found Docker version 20.10.17
Found Docker Compose version 2.6.0
▶ Turning things off ...
Warning: No resource found to remove for project "sentry-self-hosted".
Warning: No resource found to remove for project "sentry_onpremise".
▶ Creating volumes for persistent storage ...
Created sentry-clickhouse.
Created sentry-data.
Created sentry-kafka.
Created sentry-postgres.
Created sentry-redis.
Created sentry-symbolicator.
Created sentry-zookeeper.
▶ Ensuring files from examples ...
../sentry/sentry.conf.py already exists, skipped creation.
../sentry/config.yml already exists, skipped creation.
../symbolicator/config.yml already exists, skipped creation.
▶ Ensuring Relay credentials ...
../relay/config.yml already exists, skipped creation.
../relay/credentials.json already exists, skipped creation.
▶ Generating secret key ...
▶ Replacing TSDB ...
▶ Fetching and updating Docker images ...
nightly: Pulling from getsentry/sentry
Digest: sha256:0ea35f9157c0dfd69b737d2d1de75a544bb17c605b7f6dd1107680c7e3e163af
Status: Image is up to date for getsentry/sentry:nightly
docker.io/getsentry/sentry:nightly
▶ Building and tagging Docker images ...
#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 32B done
#1 DONE 0.0s
#2 [internal] load .dockerignore
#2 transferring context: 2B done
#2 DONE 0.0s
#3 [internal] load metadata for docker.io/getsentry/sentry:nightly
#3 DONE 0.0s
#4 [1/4] FROM docker.io/getsentry/sentry:nightly
#4 DONE 0.0s
#5 [internal] load build context
#5 transferring context: 297B done
#5 DONE 0.0s
#6 [3/4] RUN if [ -s /usr/src/sentry/enhance-image.sh ]; then /usr/src/sentry/enhance-image.sh; fi
#6 CACHED
#7 [2/4] COPY . /usr/src/sentry
#7 CACHED
#8 [4/4] RUN if [ -s /usr/src/sentry/requirements.txt ]; then echo "sentry/requirements.txt is deprecated, use sentry/enhance-image.sh - see https://github.com/getsentry/self-hosted#enhance-sentry-image"; pip install -r /usr/src/sentry/requirements.txt; fi
#8 CACHED
#9 exporting to image
#9 exporting layers done
#9 writing image sha256:2c9148498c31b184fb6fe48ca088dd595677daaa0369072b81205f0b223cd616 done
#9 naming to docker.io/library/sentry-self-hosted-local done
#9 DONE 0.0s
#1 [sentry-cleanup-self-hosted-local internal] load build definition from Dockerfile
#1 transferring dockerfile: 32B done
#1 DONE 0.0s
#2 [sentry-self-hosted-local internal] load build definition from Dockerfile
#2 transferring dockerfile: 32B done
#2 DONE 0.0s
#3 [symbolicator-cleanup-self-hosted-local internal] load build definition from Dockerfile
#3 transferring dockerfile: 32B done
#3 DONE 0.0s
#4 [clickhouse-self-hosted-local internal] load build definition from Dockerfile
#4 transferring dockerfile: 31B done
#4 DONE 0.0s
#5 [snuba-cleanup-self-hosted-local internal] load build definition from Dockerfile
#5 transferring dockerfile: 32B done
#5 DONE 0.0s
#6 [snuba-cleanup-self-hosted-local internal] load .dockerignore
#6 transferring context: 2B done
#6 DONE 0.0s
#7 [sentry-cleanup-self-hosted-local internal] load .dockerignore
#7 transferring context: 2B done
#7 DONE 0.0s
#8 [symbolicator-cleanup-self-hosted-local internal] load .dockerignore
#8 transferring context: 2B done
#8 DONE 0.0s
#9 [clickhouse-self-hosted-local internal] load .dockerignore
#9 transferring context: 2B done
#9 DONE 0.0s
#10 [sentry-self-hosted-local internal] load .dockerignore
#10 transferring context: 2B done
#10 DONE 0.0s
#11 [sentry-cleanup-self-hosted-local internal] load metadata for docker.io/library/sentry-self-hosted-local:latest
#11 DONE 0.0s
#12 [sentry-cleanup-self-hosted-local 1/5] FROM docker.io/library/sentry-self-hosted-local
#12 DONE 0.0s
#13 [sentry-cleanup-self-hosted-local 2/5] RUN if [ -z "${http_proxy}" ]; then echo "Acquire::http::proxy "${http_proxy}";" >> /etc/apt/apt.conf; fi
#13 CACHED
#14 [sentry-cleanup-self-hosted-local internal] load build context
#14 transferring context: 35B done
#14 DONE 0.0s
#15 [sentry-cleanup-self-hosted-local 3/5] RUN if [ -z "${https_proxy}" ]; then echo "Acquire::https::proxy "${https_proxy}";" >> /etc/apt/apt.conf; fi
#15 ...
#16 [symbolicator-cleanup-self-hosted-local internal] load metadata for docker.io/getsentry/symbolicator:nightly
#16 DONE 0.0s
#17 [symbolicator-cleanup-self-hosted-local 1/5] FROM docker.io/getsentry/symbolicator:nightly
#17 DONE 0.0s
#18 [sentry-self-hosted-local internal] load metadata for docker.io/getsentry/sentry:nightly
#18 DONE 0.0s
#19 [sentry-self-hosted-local 1/4] FROM docker.io/getsentry/sentry:nightly
#19 DONE 0.0s
#20 [snuba-cleanup-self-hosted-local internal] load metadata for docker.io/getsentry/snuba:nightly
#20 DONE 0.0s
#21 [sentry-self-hosted-local internal] load build context
#21 transferring context: 297B done
#21 DONE 0.0s
#22 [sentry-self-hosted-local 2/4] COPY . /usr/src/sentry
#22 CACHED
#23 [sentry-self-hosted-local 3/4] RUN if [ -s /usr/src/sentry/enhance-image.sh ]; then /usr/src/sentry/enhance-image.sh; fi
#23 CACHED
#24 [sentry-self-hosted-local 4/4] RUN if [ -s /usr/src/sentry/requirements.txt ]; then echo "sentry/requirements.txt is deprecated, use sentry/enhance-image.sh - see https://github.com/getsentry/self-hosted#enhance-sentry-image"; pip install -r /usr/src/sentry/requirements.txt; fi
#24 CACHED
#25 [snuba-cleanup-self-hosted-local 1/5] FROM docker.io/getsentry/snuba:nightly
#25 DONE 0.0s
#26 [snuba-cleanup-self-hosted-local 2/5] RUN if [ -z "${http_proxy}" ]; then echo "Acquire::http::proxy "${http_proxy}";" >> /etc/apt/apt.conf; fi
#26 CACHED
#27 [snuba-cleanup-self-hosted-local 3/5] RUN if [ -z "${https_proxy}" ]; then echo "Acquire::https::proxy "${https_proxy}";" >> /etc/apt/apt.conf; fi
#27 CACHED
#28 [snuba-cleanup-self-hosted-local internal] load build context
#28 transferring context: 35B done
#28 DONE 0.0s
#29 [symbolicator-cleanup-self-hosted-local 2/5] RUN if [ -z "${http_proxy}" ]; then echo "Acquire::http::proxy "${http_proxy}";" >> /etc/apt/apt.conf; fi
#29 CACHED
#30 [symbolicator-cleanup-self-hosted-local 3/5] RUN if [ -z "${https_proxy}" ]; then echo "Acquire::https::proxy "${https_proxy}";" >> /etc/apt/apt.conf; fi
#30 CACHED
#31 [symbolicator-cleanup-self-hosted-local internal] load build context
#31 transferring context: 35B done
#31 DONE 0.0s
#32 [sentry-self-hosted-local] exporting to image
#32 exporting layers done
#32 writing image sha256:2c9148498c31b184fb6fe48ca088dd595677daaa0369072b81205f0b223cd616 done
#32 naming to docker.io/library/sentry-self-hosted-local done
#32 DONE 0.1s
#33 [clickhouse-self-hosted-local internal] load metadata for docker.io/yandex/clickhouse-server:20.3.9.70
#33 DONE 1.0s
#34 [clickhouse-self-hosted-local 1/1] FROM docker.io/yandex/clickhouse-server:20.3.9.70@sha256:932ef73994dd4b6507a55a288c5ee065aae8e77e61ee569512a76a65eddbe2c3
#34 DONE 0.0s
#35 [symbolicator-cleanup-self-hosted-local 4/5] RUN apt-get update && apt-get install -y --no-install-recommends cron && rm -r /var/lib/apt/lists/*
#35 ...
#15 [sentry-cleanup-self-hosted-local 3/5] RUN if [ -z "${https_proxy}" ]; then echo "Acquire::https::proxy "${https_proxy}";" >> /etc/apt/apt.conf; fi
#15 DONE 1.2s
#34 [clickhouse-self-hosted-local 1/1] FROM docker.io/yandex/clickhouse-server:20.3.9.70@sha256:932ef73994dd4b6507a55a288c5ee065aae8e77e61ee569512a76a65eddbe2c3
#34 resolve docker.io/yandex/clickhouse-server:20.3.9.70@sha256:932ef73994dd4b6507a55a288c5ee065aae8e77e61ee569512a76a65eddbe2c3 done
#34 sha256:2910811b6c4227c2f42aaea9a3dd5f53b1d469f67e2cf7e601f631b119b61ff7 0B / 847B 0.1s
#34 sha256:abe55fc6544d42937af1eccad0a639a039bded091b0972124d3069eba82089b8 7.93kB / 7.93kB done
#34 sha256:23884877105a7ff84a910895cd044061a4561385ff6c36480ee080b76ec0e771 0B / 26.69MB 0.1s
#34 sha256:932ef73994dd4b6507a55a288c5ee065aae8e77e61ee569512a76a65eddbe2c3 2.62kB / 2.62kB done
#34 sha256:bc38caa0f5b94141276220daaf428892096e4afd24b05668cd188311e00a635f 0B / 35.37kB 0.1s
#34 sha256:bc38caa0f5b94141276220daaf428892096e4afd24b05668cd188311e00a635f 35.37kB / 35.37kB 0.4s done
#34 CANCELED
#36 [snuba-cleanup-self-hosted-local 4/5] RUN apt-get update && apt-get install -y --no-install-recommends cron && rm -r /var/lib/apt/lists/*
#0 1.169 Err:1 http://deb.debian.org/debian bullseye InRelease
#0 1.169 Temporary failure resolving 'deb.debian.org'
#0 1.171 Err:2 http://deb.debian.org/debian-security bullseye-security InRelease
#0 1.171 Temporary failure resolving 'deb.debian.org'
#0 1.171 Err:3 http://deb.debian.org/debian bullseye-updates InRelease
#0 1.171 Temporary failure resolving 'deb.debian.org'
#0 1.181 Reading package lists...
#0 1.210 W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease Temporary failure resolving 'deb.debian.org'
#0 1.210 W: Failed to fetch http://deb.debian.org/debian-security/dists/bullseye-security/InRelease Temporary failure resolving 'deb.debian.org'
#0 1.210 W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-updates/InRelease Temporary failure resolving 'deb.debian.org'
#0 1.210 W: Some index files failed to download. They have been ignored, or old ones used instead.
#0 1.223 Reading package lists...
#0 1.238 Building dependency tree...
#0 1.238 Reading state information...
#0 1.250 E: Unable to locate package cron
#36 ERROR: executor failed running [/bin/sh -c apt-get update && apt-get install -y --no-install-recommends cron && rm -r /var/lib/apt/lists/*]: exit code: 100
… and so on… lots of Temporary failure resolving 'deb.debian.org' etc.
Restarting Docker doesn’t help (as suggested e.g. here).
Автор zema, 29 апреля 2020, 16:36:25
« назад — далее »
0 Пользователи и 1 гость просматривают эту тему.
Стоит файлопомойка на Debian c 6 версии обновлял до 9 и ядра пере собирал было всё нормально. Несколько месяцев назад ( может пол года) не стал работать apt-get update Ошибка «Следующие подписи не могут быть проверены, так как недоступен открытый ключ: NO_PUBKEY «
Никакие советы из интернета не помогали. Недавно дома с нуля переставил Debian 10 настроил основные службы, принёс на работу меняю подсеть на нужную (192.168.88 на 192.168.0 ) в /etc/network/interfaces и в /etc/resolv.conf . также побывал nameserver 8.8.8.8 в /etc/resolv.conf
и получаю ошибку:
Не удалось получить http://deb.debian.org/debian/dists/buster/InRelease Временная ошибка при разрешении «deb.debian.org»
Вроде бы DNS, но ping по именам проходит. Раньше в sources.list помогало смена имён на IP, но не в этот раз.
прописываю в apt.conf прокси и получаю Ошибку «Следующие подписи не могут быть проверены, так как недоступен открытый ключ: NO_PUBKEY «
То есть с чего начал тем и закончил.
Дома остался винт с Debian (на котором всё работает) клонирую приношу на работу ситуация повторяется, ставлю на другой компьютер тоже самое.
На роутере снимал все запрещающие правила ничего не меняется. Под Windows сеть работает без вопросов.
Приношу винт домой, меняю ip и apt-get update также не работает.
В чём может быть засада?
Ошибка явно в настройках сети, где конкретно — без понятия. т.к. наворотить можно что угодно.
они где то ещё есть кроме /etc/network/interfaces /etc/resolv.conf ?
Про ошибку с подписями репозиториев — покажите список источников /etc/apt/sources.list
- Русскоязычное сообщество Debian GNU/Linux
-
►
-
►
Общие вопросы -
►
apt-get update не работает
I am on CentOS 8.
The second step in my Dockerfile tries to update the system, but for some reason, it keeps saying that it is having trouble resolving deb.debian.org and security.debian.org, so the update fails.
Step 2/13 : RUN apt-get update && apt-get -y install
---> Running in fa042e27e301
Err:1 http://security.debian.org/debian-security buster/updates InRelease
Temporary failure resolving 'security.debian.org'
Err:2 http://deb.debian.org/debian buster InRelease
Temporary failure resolving 'deb.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/debian-security/dists/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...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I tried pinging the domains it failed to resolve and it worked, so I’m confused on why it fails in the container.
I then tried creating a docker container from Debian without any other commands. Once in the new container, the same issue occurs (can’t update system), then I try pinging deb.debian.org & google.com, both times it spits out this error (when I did the same thing but on an alpine container, the ping worked, so something is wrong specifically with Debian):
ping: deb.debian.org: Temporary failure in name resolution
My /etc/docker/daemon.json:
{
"dns": ["1.1.1.1", "8.8.8.8"]
}
I have a VM with basically the same configuration, to test out containers before publishing them on my host pc. The error I’m getting above happened on my VM, but after a reboot, it fixed itself. After rebooting the host pc, the error persists.
нет DNS, судя по тексту, а может быть и сети вообще.
нужно получить корректные настройки сети.
- Ссылка
А интернет и резолвинг DNS хоть работает?
ping 8.8.8.8
ping google.com
Kron4ek ★★★★★
()
- Ссылка
ping 8.8.8.8 = Network is unreachebale
ping google.comm = Temporary failure in name resolution
Во время инсталяции установщик ругнулся на отсутствие какого-то одного файла для вайфая, но дал продолжить, и как я понимаю, потом скачивал пакеты установки из интернета. Так что я подумал, что интернет работает. А вот нет 
aroot
()
- Показать ответы
- Ссылка
Кстати, если во время установки выбрать какое-то DE, гнома или кде, то все работает.
aroot
()
- Показать ответ
- Ссылка
Ответ на:
комментарий
от aroot
ЕМНИП доступность сети при установке debian не означает, что после установки debian сеть будет работать
anonymous
()
- Ссылка
Ответ на:
комментарий
от aroot
В DE обычно интегрирован NetworkManager – вот сеть и работает. Без DE ты сам должен собрать* поддержку сети (и не обязательно с помощью NetworkManager)
anonymous
()
- Ссылка
Хорошо, понял, буду разбираться. Спасибо за помощь.
Ветку закрываю тогда.
aroot
()
- Ссылка
Ответ на:
комментарий
от aroot
Во время инсталяции установщик ругнулся на отсутствие какого-то одного файла для вайфая
Он ругнулся на фирмварю для вафли- в штатном дебиане нет блобов, тебе нужен либо образ с блобами либо просто установить пакет с нужным блобом после установки с обычного образа — смотришь какой у тебя контроллер в вафле, гуглишь в каком пакете лежит блоб для него (там по сути всего 3-4 варианта для наиболее распространённых), качаешь его на флешку и ставишь на целевой машинке.
После чего ребутишься и настраиваешь сетку, если ставил минимал то у тебя как минимум есть wpa_supplicant
rukez ★★★★
()
- Показать ответ
- Ссылка
Ответ на:
комментарий
от rukez
Ответ на:
комментарий
от rukez
Ответ на:
комментарий
от rukez
Тут образы с блобами: https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/
Да, я отсюда и брал iso.
Я пробовал ставить stable Дебиан 10.8 и testing Debian 11. Оба дистрибутива брал с firmware, потому что обычный дистрибутив ни 10, ни 11 не видели мою интеловскую карту вайфай на ноутбуке HP.
Если устанавливать Дебиан 10, то установщик ни на что не ругается, все в порядке. Спокойно качает пакеты с интернета во время установки. Если установить DE, то вообще все работает. Если без DE — как объяснили, мне надо самому настроить параметры сети. Я пока этого не сделал.
Если устанавливать Дебиан 11, то все как на 10, плюс ругается, что нет на флешке какого-то файла для карты вайфай. Но сетку ловит, качает пакеты для установки. И тоже, если установить DE — все полностью работает, а если без DE — надо настраивать параметры сети.
aroot
()
- Показать ответ
- Ссылка
если совсем никак а debian хочется то смотри в сторону based дистров типа lmde, mx linux, antix, devuan
anonymous
()
- Ссылка
Ответ на:
комментарий
от aroot
плюс ругается, что нет на флешке какого-то файла для карты вайфай
Ещё стоит убедится что в папке firmware лежат не Файлы нулевой длинны — у меня после руфуса стабильно так почему то
А сеть да, надо настраивать с нуля, самый простой способ, после подтыкивания пакета с фирмварью (обычно это misc) закинуть в /etc/network/interfaces настройки точки с открытым паролем, ребутнуть машину (если фирмварь подцепится сразу то можно systemctl restart networking), навернуть де по вкусу с сетевым менеджером по вкусу (для пустого гнома, например gnome-core оно сразу с манагером идёт), потом затереть набранное в interfaces и после ребута получить готовую систему
rukez ★★★★
()
- Показать ответ
- Ссылка
Ответ на:
комментарий
от rukez
Да, все сделал.
Порядок такой:
-
Установил Дебиан без DE. Перезагрузка.
-
sudo iwconfig
Находим как определяется вайфай сеть. У меня wlo1
- sudo sensible-editor /etc/network/interfaces
Дописываем следующее содержание:
auto wlo1 где wlo1 — определяем из пункта 2
iface wlo1 inet dhcp где wlo1 — определяем из пункта 2
wpa-ssid тут указываем идентификатор сети вайфая
wpa-psk тут указываем пароль
Записываем изменения
-
sudo ifup wlo1 где wlo1 — определяем из пункта 2
-
sudo /etc/init.d/networking restart
-
ping 8.8.8.8 Проверяем наличие интернета
У меня так все начало работать.
Это решение не самое безопасное, но простое.
Спасибо всем кто помог советом!
aroot
()
- Показать ответы
- Ссылка
Из-за голосования ихнего многие от Debian уйдут наверное и их поглотит Canonical Ubuntu
anonymous
()
- Ссылка
Ответ на:
комментарий
от aroot
Это решение из 2003, на современном десктопе никто вручную вайфай не полнимает)
- Ссылка
Ответ на:
комментарий
от aroot
боже, какое же дебиан говно, просто ужас
anonymous
()
- Ссылка
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.