Error in Dockerfile + Temporary failure resolving 'deb.debian.org' - docker

I have a Dockerfile but it gets an error when I want to build it. my Dockerfile is :
FROM php:7.4.8-fpm
ENV APP_HOME /var/www/html
# install all the dependencies and enable PHP modules
RUN apt-get update && apt-get upgrade -y && apt-get install -y
I get the following errors:
Err:1 http://httpredir.debian.org/debian jessie-backports InRelease
Temporary failure resolving 'httpredir.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 InRelease
Temporary failure resolving 'deb.debian.org'
Err:4 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: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/InRelease Temporary failure resolving 'httpredir.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

Related

The repository 'http://ppa.launchpad.net/chris-lea/node.js/ubuntu focal Release' does not have a Release file on ROR

While execution the sudo apt-get update I am getting bellow error on terminal.
Err:10 http://ppa.launchpad.net/chris-lea/node.js/ubuntu focal Release
404 Not Found [IP: 2620:2d:4000:1::3e 80]
Get:11 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Hit:12 http://in.archive.ubuntu.com/ubuntu focal InRelease
Hit:13 http://in.archive.ubuntu.com/ubuntu focal-updates InRelease
Get:14 http://in.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/chris-lea/node.js/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
I tried few steps but, those not working.
For resolving the above error what we have to do?
enter image description here

Docker image ubuntu:21.10 produces The repository 'http://security.ubuntu.com/ubuntu impish-security Release' does not have a Release file

I am creating a docker image FROM ubuntu:21.10
All worked fine a couple of weeks ago but today I get:
Step 3/76 : RUN apt-get update && apt-get -y upgrade
---> Running in 7f2afb2074e8
Ign:1 http://archive.ubuntu.com/ubuntu impish InRelease
Ign:2 http://security.ubuntu.com/ubuntu impish-security InRelease
Ign:3 http://archive.ubuntu.com/ubuntu impish-updates InRelease
Err:4 http://security.ubuntu.com/ubuntu impish-security Release
404 Not Found [IP: 91.189.91.38 80]
Ign:5 http://archive.ubuntu.com/ubuntu impish-backports InRelease
Err:6 http://archive.ubuntu.com/ubuntu impish Release
404 Not Found [IP: 91.189.91.39 80]
Err:7 http://archive.ubuntu.com/ubuntu impish-updates Release
404 Not Found [IP: 91.189.91.39 80]
Err:8 http://archive.ubuntu.com/ubuntu impish-backports Release
404 Not Found [IP: 91.189.91.39 80]
Reading package lists...
E: The repository 'http://security.ubuntu.com/ubuntu impish-security Release' does not have a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu impish Release' does not have a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu impish-updates Release' does not have a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu impish-backports Release' does not have a Release file.
I have been looking around to fix it but I really don't know how.
Any help is appreciated
In your dockerfile try using ubuntu:jammy, that worked fine for me.

Error when installing ROS Noetic. 404 Not Found [IP: 91.189.95.85 80]

Hit:1 http://archive.canonical.com/ubuntu focal InRelease
Hit:2 http://ca.archive.ubuntu.com/ubuntu focal InRelease
Hit:3 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:4 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:5 http://packages.ros.org/ros/ubuntu focal InRelease
Ign:6 http://ppa.launchpad.net/gnome-terminator/ppa/ubuntu focal InRelease
Hit:7 https://download.sublimetext.com apt/stable/ InRelease
Hit:8 http://security.ubuntu.com/ubuntu focal-security InRelease
Err:9 http://ppa.launchpad.net/gnome-terminator/ppa/ubuntu focal Release
404 Not Found [IP: 91.189.95.85 80]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/gnome-terminator/ppa/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Im getting this error when installing ROS on my Dell XPS 13. Im new to all of this so any help is appreciated. I other solutions but they work.
thanks
What's your OS? which installation commands have you executed?
The error seems to be with the gnome-terminator ppa. Try disabling it.

Docker build failing on private hosted agent (Azure DevOps)

I am trying to build a dockerfile on a private-hosted Azure DevOps agent, which is behind a corporate proxy. The base image is python/3.8.3-slim-buster. When I run apt-get update I get the following errors:
Err:1 http://deb.debian.org/debian buster InRelease
470 status code 470 [IP: 151.101.36.204 80]
Err:2 http://security.debian.org/debian-security buster/updates InRelease
470 status code 470 [IP: 151.101.36.204 80]
Err:3 http://deb.debian.org/debian buster-updates InRelease
470 status code 470 [IP: 151.101.36.204 80]
Reading package lists...
E: The repository 'http://deb.debian.org/debian buster InRelease' is not signed.
E: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease 470 status code 470 [IP: 151.101.36.204 80]
E: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease 470 status code 470 [IP: 151.101.36.204 80]
E: The repository 'http://security.debian.org/debian-security buster/updates InRelease' is not signed.
E: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease 470 status code 470 [IP: 151.101.36.204 80]
E: The repository 'http://deb.debian.org/debian buster-updates InRelease' is not signed.
Now the tricky part is that if I log in to this agent manually, and give the docker build command there it works fine. Also building on a Microsoft hosted agent works fine.
I pass the proxy configuration with --build-arg flags to the Dockerfile.
Anyone any idea where the error could be?
Edit:
I tried adding the "--allow-releaseinfo-change" flag, still the same error. I have the feeling it somehow proxy related but can't figure out where to start looking.
Today I learned apt-get keeps the proxy-configuration somewhere else, as in my environment variables HTTP_PROXY & HTTPS_PROXY were not picked up.
Creating a proxy.conf and copying that to the container solved my problem as mentioned here:
https://www.serverlab.ca/tutorials/linux/administration-linux/how-to-set-the-proxy-for-apt-for-ubuntu-18-04/

Proxy for docker under windows 10 only works for http, but not for https

for quite a while I try to build a Dockerfile, but get therefore I need necessary not packages from Nvidia, which are fetched from a https link.
Since this I have to use proxy I set the following variables in the dockerfile:
ENV http_proxy http://proxy:0000
ENV https_proxy https://user:password#proxy:0000
If I do not add a user and a password to the https proxy, then I get the HTTP 407 error , which means an authentication failure. If I include a use and password I get the following error:
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:5 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [801 kB]
Ign:6 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 InRelease
.
.
.
Ign:24 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1604/x86_64 Packages
Ign:16 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 Packages
Ign:24 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1604/x86_64 Packages
Ign:16 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 Packages
Ign:24 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1604/x86_64 Packages
Ign:16 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 Packages
Ign:24 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1604/x86_64 Packages
Err:16 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Err:24 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1604/x86_64 Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Fetched 15.7 MB in 3s (3984 kB/s)
Reading package lists...
W: The repository 'https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64 Release' does not have a Release file.
W: The repository 'https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1604/x86_64 Release' does not have a Release file.
E: Failed to fetch https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Failed to fetch https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1604/x86_64/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.
So the proxy for http works, but not for https. I guess it is something with the ssl certificates as metnioned in the rror, but I can not find anything useful for this topic. Btw. this is a windows issue, obviously under Linux everything worked fine.

Resources