I am trying to upgrade one of our docker base images to the latest stable version of Ubuntu. I have isolated the problem to a simple reproducible case. I have a Dockerfile like this:
FROM ubuntu:22.04
MAINTAINER mep-dev#zulily.com
# Install java and clean-up
RUN apt-get update
When I build it on my local machine, I don't have any problems. However, when I build it on my CICD, I sometimes get this error:
Step 3/3 : RUN apt-get update
---> Running in 6ca01b60de64
Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [109 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Reading package lists...
W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.
W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed.
E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/.deb /var/cache/apt/archives/partial/.deb /var/cache/apt/*.bin || true'
E: Sub-process returned an error code
The command '/bin/sh -c apt-get update' returned a non-zero code: 100
If I comment out RUN apt-get update, then it succeeds, and I can enter the container and see that /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg and /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg do exist and have read for all permissions:
root#b778220b39d8:/# ls -l /etc/apt/trusted.gpg.d
total 8
-rw-r--r-- 1 root root 2794 Mar 26 2021 ubuntu-keyring-2012-cdimage.gpg
-rw-r--r-- 1 root root 1733 Mar 26 2021 ubuntu-keyring-2018-archive.gpg
I also checked the parent directories, and they have r-x at least for all.
This answer might be related, but why would the file have the correct structure when the base image is used in one environment and not another?
Update:
By using --pull, I can see the exact image it's using.
$ docker build --pull -t $EMAIL_DELIVERABILITY_ARN .
Step 1/3 : FROM ubuntu:22.04
22.04: Pulling from library/ubuntu
Digest: sha256:b6b83d3c331794420340093eb706a6f152d9c1fa51b262d9bf34594887c2c7ac
Status: Downloaded newer image for ubuntu:22.04
---> 27941809078c
This is the same sha and image id that I see when building locally, which works.
I am not having the same problem with ubuntu:20.04.
After spending half a day trying to fix the Ubuntu images (which aren't broken) I have eventually started debugging the host.
It's a docker problem. Ubuntu makes use of syscalls for better key security, which Docker didn't support yet. The solution is to update docker... or use runc or something similar.
Instead of apt getting the message that the syscalls aren't supported, it gets the message that permission is denied, which results in the confusing error messages.
You could technically patch ubuntu to be less secure, and to work with older docker, but that is sadly not a long term solution.
When you reference a docker image by name, Docker only checks to see if it exists locally or not -- it doesn't check for updates. So if there is already a version of the named image available, it will use that even though it might be stale. I suspect that's what you're seeing: some of your CI nodes must have a cached version of the image that has problems.
There are a few ways of dealing with this:
Explicitly docker pull ubuntu:22.04 before calling docker run; this will pull down a newer version of the image if one exists.
Add --pull always to your docker run command line. This accomplishes the same thing but without requiring an extra command execution.
Reference an image by digest rather than by tag. If you use an image reference like this:
FROM ubuntu#sha256:bace9fb0d5923a675c894d5c815da75ffe35e24970166a48a4460a48ae6e0d19
Then docker will use that exact image. You can find the image digests on docker hub.
Exactly same problem
Err:3 http://security.ubuntu.com/ubuntu jammy-security InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Reading package lists...
[91mW: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
Dockerfile (simple how to reproduce) docker-version: 18.x or 19.03/
FROM ubuntu:latest
RUN apt-get -y update
With latest Docker version 20.10.9, i did not see the issue.
some of the options tried to tshoot:
sed -i 's/jammy/focal/g' /etc/apt/sources.list
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 871920D1991BC93C
this fails with with another child-issue
gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
SO, solutions seems to be either update docker-version or use a tagged image where it has worked previously.
A very dirty but probably acceptable hack for some docker hacking is this:
apt update --allow-insecure-repositories
Which just ignores the signatures. The errors get still printed, but the package repository is updated, and you can install new packages afterwards. Even though you get warned and asked if that is really what you want to do.
It is the same from me, something is broken inside the Ubuntu image. The issue is not coming from the docker software/pkg, it is sourced within the image.
Related
I am facing issues while installing the latest ruby version 2.7.1
When I try to run the command rvm install 2.7.1
Warning, new version of rvm available '1.29.10', you are using older version '1.29.9'.
You can disable this warning with: echo rvm_autoupdate_flag=0 >> ~/.rvmrc
You can enable auto-update with: echo rvm_autoupdate_flag=2 >> ~/.rvmrc
You can update manually with: rvm get VERSION (e.g. 'rvm get stable')
Searching for binary rubies, this might take some time.
Found remote file https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/18.04/x86_64/ruby-2.7.1.tar.bz2
Checking requirements for ubuntu.
Installing requirements for ubuntu.
Updating system........There has been an error while updating your system using `apt-get`.
It seems that there are some 404 Not Found errors for repositories listed in:
. /etc/apt/sources.list
/etc/apt/sources.list.d/*.list
\
Make sure that all repositories are available from your system and verify your setup by running manually:
sudo apt-get update
-
Make sure that it works correctly before proceeding with RVM.
|
If you are working from the GUI instead of the terminal, you might want to verify and fix broken
repositories using "Software & Updates" application.
.
.
Error running 'requirements_debian_update_system ruby-2.7.1',
please read /home/anikettiwari/.rvm/log/1592545564_ruby-2.7.1/update_system.log
Requirements installation failed with status: 100.
When I try to run sudo apt-get update. It didn't help either
Hit:1 http://ppa.launchpad.net/audio-recorder/ppa/ubuntu bionic InRelease
Hit:2 https://dl.yarnpkg.com/debian stable InRelease
Hit:3 http://in.archive.ubuntu.com/ubuntu bionic InRelease
Hit:4 http://in.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:5 http://in.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:6 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:7 http://ppa.launchpad.net/peek-developers/stable/ubuntu bionic InRelease
Hit:8 http://security.ubuntu.com/ubuntu bionic-security InRelease
Ign:9 http://ppa.launchpad.net/sethj/silentcast/ubuntu bionic InRelease
Hit:10 https://download.sublimetext.com apt/stable/ InRelease
Hit:11 https://deb.nodesource.com/node_12.x bionic InRelease
Hit:12 https://dbeaver.io/debs/dbeaver-ce InRelease
Hit:13 http://ppa.launchpad.net/videolan/master-daily/ubuntu bionic InRelease
Hit:14 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:15 https://repo.skype.com/deb stable InRelease
Err:16 http://ppa.launchpad.net/sethj/silentcast/ubuntu bionic Release
404 Not Found [IP: 2001:67c:1560:8008::15 80]
Reading package lists... Done
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Translations (main/i18n/Translation-en_IN) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://dl.google.com/linux/chrome/deb stable InRelease' doesn't support architecture 'i386'
E: The repository 'http://ppa.launchpad.net/sethj/silentcast/ubuntu bionic 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.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Translations (main/i18n/Translation-en_IN) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
I try to check the logs as mentioned
cat /home/anikettiwari/.rvm/log/1592547152_ruby-2.7.1/update_system.log
[2020-06-19 11:42:32] requirements_debian_update_system
requirements_debian_update_system ()
{
__rvm_try_sudo apt-get --quiet --yes update || {
\typeset __ret=$?;
case ${__ret} in
100)
rvm_error "There has been an error while updating your system using \`apt-get\`.
It seems that there are some 404 Not Found errors for repositories listed in:
/etc/apt/sources.list
/etc/apt/sources.list.d/*.list
Make sure that all repositories are available from your system and verify your setup by running manually:
sudo apt-get update
Make sure that it works correctly before proceeding with RVM.
If you are working from the GUI instead of the terminal, you might want to verify and fix broken
repositories using \"Software & Updates\" application.
"
;;
esac;
return ${__ret}
}
}
current path: /home/anikettiwari/Desktop
GEM_HOME=/home/anikettiwari/.rvm/gems/ruby-2.5.3
GEM_PATH=/home/anikettiwari/.rvm/gems/ruby-2.5.3:/home/anikettiwari/.rvm/gems/ruby-2.5.3#global
PATH=/home/anikettiwari/.rvm/gems/ruby-2.5.3/bin:/home/anikettiwari/.rvm/gems/ruby-2.5.3#global/bin:/home/anikettiwari/.rvm/rubies/ruby-2.5.3/bin:/home/anikettiwari/.rvm/bin:/home/anikettiwari/anaconda3/condabin:/home/anikettiwari/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
command(2): requirements_debian_update_system ruby-2.7.1
++ __rvm_try_sudo apt-get --quiet --yes update
++ typeset -a command_to_run
++ typeset sudo_path sbin_path missing_paths
++ command_to_run=("$#")
++ (( UID == 0 ))
++ case "$rvm_autolibs_flag_number" in
++ is_a_function __rvm_sudo
++ typeset -f __rvm_sudo
++ missing_paths=
++ for sbin_path in /sbin /usr/sbin /usr/local/sbin
++ [[ -d /sbin ]]
++ [[ :/home/anikettiwari/.rvm/gems/ruby-2.5.3/bin:/home/anikettiwari/.rvm/gems/ruby-2.5.3#global/bin:/home/anikettiwari/.rvm/rubies/ruby-2.5.3/bin:/home/anikettiwari/.rvm/bin:/home/anikettiwari/anaconda3/condabin:/home/anikettiwari/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin: != *\:\/\s\b\i\n\:* ]]
++ for sbin_path in /sbin /usr/sbin /usr/local/sbin
++ [[ -d /usr/sbin ]]
++ [[ :/home/anikettiwari/.rvm/gems/ruby-2.5.3/bin:/home/anikettiwari/.rvm/gems/ruby-2.5.3#global/bin:/home/anikettiwari/.rvm/rubies/ruby-2.5.3/bin:/home/anikettiwari/.rvm/bin:/home/anikettiwari/anaconda3/condabin:/home/anikettiwari/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin: != *\:\/\u\s\r\/\s\b\i\n\:* ]]
++ for sbin_path in /sbin /usr/sbin /usr/local/sbin
++ [[ -d /usr/local/sbin ]]
++ [[ :/home/anikettiwari/.rvm/gems/ruby-2.5.3/bin:/home/anikettiwari/.rvm/gems/ruby-2.5.3#global/bin:/home/anikettiwari/.rvm/rubies/ruby-2.5.3/bin:/home/anikettiwari/.rvm/bin:/home/anikettiwari/anaconda3/condabin:/home/anikettiwari/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin: != *\:\/\u\s\r\/\l\o\c\a\l\/\s\b\i\n\:* ]]
++ [[ -n '' ]]
++ command_to_run=(__rvm_sudo -p "%p password required for '$*': " "${command_to_run[#]}")
++ __rvm_sudo -p '%p password required for '\''apt-get --quiet --yes update'\'': ' apt-get --quiet --yes update
++ command sudo -p '%p password required for '\''apt-get --quiet --yes update'\'': ' apt-get --quiet --yes update
++ sudo -p '%p password required for '\''apt-get --quiet --yes update'\'': ' apt-get --quiet --yes update
Hit:1 http://ppa.launchpad.net/audio-recorder/ppa/ubuntu bionic InRelease
Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:3 https://dl.yarnpkg.com/debian stable InRelease
Hit:4 http://in.archive.ubuntu.com/ubuntu bionic InRelease
Hit:5 http://in.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:6 http://in.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:7 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:8 http://ppa.launchpad.net/peek-developers/stable/ubuntu bionic InRelease
Ign:9 http://ppa.launchpad.net/sethj/silentcast/ubuntu bionic InRelease
Hit:10 https://download.sublimetext.com apt/stable/ InRelease
Hit:11 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:12 http://ppa.launchpad.net/videolan/master-daily/ubuntu bionic InRelease
Hit:13 https://deb.nodesource.com/node_12.x bionic InRelease
Hit:14 https://repo.skype.com/deb stable InRelease
Hit:15 https://dbeaver.io/debs/dbeaver-ce InRelease
Err:16 http://ppa.launchpad.net/sethj/silentcast/ubuntu bionic Release
404 Not Found [IP: 2001:67c:1560:8008::15 80]
Reading package lists...
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Translations (main/i18n/Translation-en_IN) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
E: The repository 'http://ppa.launchpad.net/sethj/silentcast/ubuntu bionic Release' does not have a Release file.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Translations (main/i18n/Translation-en_IN) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google-chrome.list:4
++ return 100
++ typeset __ret=100
++ case ${__ret} in
++ rvm_error 'There has been an error while updating your system using `apt-get`.
It seems that there are some 404 Not Found errors for repositories listed in:
/etc/apt/sources.list
/etc/apt/sources.list.d/*.list
Make sure that all repositories are available from your system and verify your setup by running manually:
sudo apt-get update
Make sure that it works correctly before proceeding with RVM.
If you are working from the GUI instead of the terminal, you might want to verify and fix broken
repositories using "Software & Updates" application.
'
++ rvm_pretty_print stderr
++ case "${rvm_pretty_print_flag:=auto}" in
++ case "${TERM:-dumb}" in
++ case "$1" in
++ [[ -t 2 ]]
++ return 1
++ printf %b 'There has been an error while updating your system using `apt-get`.
It seems that there are some 404 Not Found errors for repositories listed in:
/etc/apt/sources.list
/etc/apt/sources.list.d/*.list
Make sure that all repositories are available from your system and verify your setup by running manually:
sudo apt-get update
Make sure that it works correctly before proceeding with RVM.
If you are working from the GUI instead of the terminal, you might want to verify and fix broken
repositories using "Software & Updates" application.
\n'
++ return 100
I am bit puzzled right now what needs to be done in order to resolve this issue
The problem is: ppa:sethj/silentcast
This PPA is not compatible with Ubuntu 18.04 (bionic).
To remove it run:
$ sudo add-apt-repository --remove ppa:sethj/silentcast
Also, you may find this guide useful: Best GIF Recorder Tools for Linux.
I got the Similar Error But while Installing diffrent version of ruby 2.3.4
I got the suggestion that Run following command to fix it up
sudo apt-get update
But that didnt work either i started getting issue in that
For fix it up i comment on the line that causing the issue in the list
Formate of command will be like this sudo nano path/*.list
sudo nano /etc/apt/sources.list.d/*.list
it will open all the files one by one and then comment the line and save the list
<pre>Err:12 http://ppa.launchpad.net/gnome-terminator/ppa/ubuntu bionic Release </pre>
after the save file when i run again update comamnd it work like a charm
The code below works for me
$ rvm autolibs homebrew
rvm autolibs read-only
for ubuntu 18.04 use the above code.
The code below works for me
rvm autolibs homebrew
rvm autolibs read-only
Build Errors unable to find jq.
Err http://deb.debian.org jessie/main amd64 Packages
404 Not Found
Err http://deb.debian.org jessie-updates/main amd64 Packages
404 Not Found
Fetched 723 kB in 2s (357 kB/s)
W: Failed to fetch http://deb.debian.org/debian/dists/jessie/main/binary-amd64/Packages 404 Not Found
W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
$ apt-get install jq
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package jq
ERROR: Job failed: exit code 1
#codinghaus mentioned in another thread:
This is due to the fact that
as Wheezy and Jessie have been integrated into the archive.debian.org structure recently, we are now removing all of Wheezy and all non-LTS architectures of Jessie from the mirror network starting today.
A solution (according to https://github.com/debuerreotype/docker-debian-artifacts/issues/66#issuecomment-476616579) is to add the following command into your Dockerfile before calling any apt-get update when using debian:jessie.
RUN sed -i '/jessie-updates/d' /etc/apt/sources.list # Now archived
This will remove the jessie-updates repository (which now causes the 404) from sources.list.
FROM debian:jessie
RUN sed -i '/jessie-updates/d' /etc/apt/sources.list # Now archived
RUN apt-get update
CMD /bin/sh
Just place this line before your apt-get commands in your Dockerfile:
RUN echo "deb http://deb.debian.org/debian jessie main" > /etc/apt/sources.list
Debian removed some url for old packages which is causing this issue. The line fixes the repository to refer to.
I had the same problem today. I believe yours is related to Jessie being removed from Debian (see: https://twitter.com/debian/status/1109080168318926851?s=12).
I upgraded php in Dockerfile to php:7.1.27-apache-stretch and it worked.
Maybe, the third party import that you are doing is not able to refer to the debian jessie, so changing ftp.debian.org to http://ftp.us.debian.org might make it work. If you are not referring to this directly, try upgrading or downgrading the imported versions, if removing them is not the option.
In my case, i was using:
FROM docker.***.com/node:10
downgrading the node from 10 to 8, kicked off the job successfully.
I'm trying to install Docker CE 18.03 on Ubuntu 18.04 using the official step by step page found here. I am stuck at step 4) sudo apt-get update. This is what I get:
Hit:1 http://mirror.transip.net/stack/software/deb/Ubuntu_18.04 ./ InRelease
Hit:2 http://nl.archive.ubuntu.com/ubuntu bionic InRelease
Ign:3 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 http://dl.google.com/linux/chrome/deb stable Release
Hit:5 http://nl.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:6 http://nl.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:7 http://security.ubuntu.com/ubuntu bionic-security InRelease
Err:8 https://get.docker.com/ubuntu docker InRelease
403 Forbidden [IP: 52.85.58.66 443]
Reading package lists... Done
E: Failed to fetch http://get.docker.io/ubuntu/dists/docker/InRelease 403 Forbidden [IP: 52.85.58.66 443]
E: The repository 'http://get.docker.io/ubuntu docker InRelease' is not signed.
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.
Visiting the link in Err:8 https://get.docker.com/ubuntu/ outputs the following:
echo "# WARNING! This script is deprecated. Please use the script"
echo "# at https://get.docker.com/"
exit 1
Ok, obsolete link, no problem, so I download the script found at get.docker.com and run it with bash, this is the result:
# Executing docker install script, commit: 36b78b2
+ sudo -E sh -c apt-get update -qq >/dev/null
E: The repository 'http://ppa.launchpad.net/colingille/freshlight/ubuntu bionic Release' does not have a Release file.
E: Failed to fetch http://get.docker.io/ubuntu/dists/docker/InRelease 403 Forbidden [IP: 52.85.58.48 443]
E: The repository 'http://get.docker.io/ubuntu docker InRelease' is not signed.
Is there anything I can try?
The installation is indeed broken and i faced it too. This link came to my rescue while I was performing similar action some time back https://gist.github.com/levsthings/0a49bfe20b25eeadd61ff0e204f50088
This error means it is not able to connect to the url mentioned..
I solved using below steps..
found out which file it is there
cd /etc/apt
grep -irl "docker"
sources.list.d/docker.list
vi sources.list.d/docker.list
change the content inside this file to
deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable
save it
and then try update again.
Solved my issue!
This error means it is not able to connect to the url mentioned..
I solved using below steps..
found out which file it is there
cd /etc/apt
grep -irl "docker"
sources.list.d/docker.list
gedit sources.list.d/docker.list
change the content inside this file to
deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable
save it
and then try update again.
Solved my issue!
You're accessing from a country that Docker blocked on their server, or at least your IP 52.85.58.66
Try to use a VPN and see it if still get you the same error.
I am trying to install ffmpeg in dockerfile.
For that, I am using following this link . Please, have look at the link before answering.
Following the answer given to that link, I am using these commands,,,
RUN apt-get install -y software-properties-common
RUN add-apt-repository -y ppa:mc3man/trusty-media
RUN apt-get update
RUN apt-get install -y ffmpeg RUN apt-get install -y frei0r-plugins
After successfully executing first two commands, apt-get update fails miserably.
Hit://deb.debian.org jessie Release.gpg
Err://ppa.launchpad.net jessie/main amd64 Packages Get:3
://security.debian.org jessie/updates/main amd64 Packages [589 kB]
Hit://deb.debian.org jessie Release
Err://ppa.launchpad.net jessie/main amd64 Packages Err
://ppa.launchpad.net jessie/main amd64 Packages Get:4
://deb.debian.org jessie-updates/main amd64 Packages [23.0 kB]
Err://ppa.launchpad.net jessie/main amd64 Packages Get:5
http://deb.debian.org jessie/main amd64 Packages [9098 kB]
Err ://ppa.launchpad.net jessie/main amd64 Packages
404 Not Found
Fetched 9900 kB in 8s (1161 kB/s)
W: Failed to fetch
http://ppa.launchpad.net/mc3man/trusty-media/ubuntu/dists/jessie/main/binary-amd64/Packages
404 Not Found
E: Some index files failed to download. They have been ignored, or old
ones used instead.
And I understood the reason that why it fails .
I would have certainly followed the solution given in the above link. Since I am working on docker. I can't do much. is there any other way to install FFMPEG on docker with all it's tools and functionalities ?
Moreover, I wasn't able to post the acutal content of the error, due to constrain that " I can't post more than 8 links , since my ratings are low." .
so in the error log, there is 'http' , before '://'.
I want to install Passenger server on my virtual machine, so I do the following:
sudo sh -c "echo 'deb https://oss-binaries.phusionpassenger.com/apt/passenger trusty main' >> /etc/apt/sources.list.d/passenger.list"
sudo chown root: /etc/apt/sources.list.d/passenger.list
sudo chmod 600 /etc/apt/sources.list.d/passenger.list
But after I update
sudo apt-get update
I get this errors:
Err https://oss-binaries.phusionpassenger.com trusty/main amd64 Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Err https://oss-binaries.phusionpassenger.com trusty/main i386 Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Ign https://oss-binaries.phusionpassenger.com trusty/main Translation-en_US
Ign https://oss-binaries.phusionpassenger.com trusty/main Translation-en
Fetched 2,573 kB in 11s (220 kB/s)
W: Failed to fetch https://oss-binaries.phusionpassenger.com/apt/passenger/dists/trusty/main/binary-amd64/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
W: Failed to fetch https://oss-binaries.phusionpassenger.com/apt/passenger/dists/trusty/main/binary-i386/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.
I already installed it previously many times and had no problems. I have no idea what might go wrong.
1) Try to re-install certificates as described here. Maybe they has been changed.
2) Look at this post. It describe similar problem and possible solutions.
Fixed that by reinstalling Ubuntu on clean VM.
This issue might appeared because I copied my VM's without turning it off.
Another possible solution is to disable peer-verification
Possible Docker Command could be:
RUN echo 'Acquire::https::oss-binaries.phusionpassenger.com::Verify-Peer "false";' > /etc/apt/apt.conf.d/99phusionpassenger-cert
You may also like to read the solution posted on another thread: server certificate verification failed