Unable to update the packages on WSL distribution [closed] - linux

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I'm using Docker desktop v2.3.0 and I enabled WSL2 on Windows 10 Professional v1909.
I installed Ubuntu 20.04 distribution, I accessed it and when I run apt-get update:
Err:1 http://archive.ubuntu.com/ubuntu focal InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu focal-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
I tried to update the /etc/resolve.conf by adding the company dns server after using ipconfig /all.
Then I rebooted the WSL but does not work.
I found a similar question No internet connection on WSL Ubuntu (Windows Subsystem for Linux) and tried this solution but none of them fixed the issue for me.
I use a proxy to access the internet, can it forbid the WSL from accessing the external network and should add it the wsl config file?

Related

Release file not found error encountered with Ubuntu 22.04 [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last month.
Improve this question
I have seen some similar questions, but in my case the following error popped up when I ran sudo apt-get update:
ICON_lab) randychen#randychen-Delta-15-A5EFK:~/projects$ sudo apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
Ign:3 http://packages.ros.org/ros/ubuntu jammy InRelease
Err:4 http://packages.ros.org/ros/ubuntu jammy Release
404 Not Found [IP: 140.211.166.134 80]
Get:5 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Get:6 http://www.deb-multimedia.org jessie InRelease [15.4 kB]
Hit:7 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:8 http://security.ubuntu.com/ubuntu jammy-security InRelease
Get:9 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [95.1 kB]
Get:10 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [257 kB]
Get:11 http://us.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
Get:13 http://us.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [11.4 kB]
Ign:6 http://www.deb-multimedia.org jessie InRelease
Hit:12 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Reading package lists... Done
E: The repository 'http://packages.ros.org/ros/ubuntu jammy 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: GPG error: http://www.deb-multimedia.org jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5C808C2B65558117
E: Release file for http://www.deb-multimedia.org/dists/jessie/InRelease is expired (invalid since 388d 20h 52min 20s). Updates for this repository will not be applied.
W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
At first I thought it's due to a PPA but I don't have any here. I tried trouble shooting it by following this post, and I added that line of code on the top of the file, but it's not working either.
Any help is greatly appreciated!
You have to correct the url:
sudo grep -rlF 'http://packages.ros.org' /etc/apt/sources* |
xargs sed -i 's#http://packages.ros.org#https://ubuntu.osuosl.org/#'
sudo apt update

"The repository does not have a Release file" error on Debian 11 (bullseye) even though the repository has a Release file [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 months ago.
The community reviewed whether to reopen this question 7 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I have Debian 11 (bullseye) installed on my raspberry pi4, I tried to install Docker following the official guide using the repository but I got stuck on the update after setting up the repository.
When I try to update, I get this as an output:
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Ign:5 https://download.docker.com/linux/debian \ InRelease
Err:6 https://download.docker.com/linux/debian \ Release
404 Not Found [IP: 13.226.175.74 443]
Reading package lists... Done
E: The repository 'https://download.docker.com/linux/debian \ 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.
From what I understand it's searching for the binary for Debian in https://download.docker.com/linux/debian
Even though the binary isn't there but I found it in https://download.docker.com/linux/debian/dists/bullseye/
And also in
https://download.docker.com/linux/debian/dists/bullseye/stable/ where there is a Release file for a bunch of architectures.
I tried changing the URL in sources.list.d/docker.list but it didn't work.
I also don't understand why the given URL gives a 404 error when the site obviously exists.
I'm just dumb...
echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian \
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
I didn't remove the second back slash...
Hope this helps someone else other than me

Docker: ubuntu:22.04 (ubuntu:latest) fails at apt update [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 10 months ago.
Improve this question
Running:
docker run -it ubuntu:22.04 /bin/bash
apt update
Fails with:
22.04: Pulling from library/ubuntu
Digest: sha256:7599221e4e2e4eeb90ad282fc523139578f3dfea245b5049c4fee1b28776d2be
Status: Downloaded newer image for ubuntu:22.04
root#117960ca68dd:/# apt update
Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [90.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [90.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [90.7 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [17.5 MB]
Get:6 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1792 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [266 kB]
Get:8 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [164 kB]
Fetched 20.2 MB in 2s (9747 kB/s)
Reading package lists... Done
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
Pulling ubuntu:21.10 still works fine.
What is causing this and how can it be avoided?
Been using docker:latest since over a year and 1st time things completely broke down during a new deploy due to the assumption that an official docker image 'just works'.

getting timeout connecting to http://br.archive.ubuntu.com/ubuntu [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Hi guys i'm having the following problem running sudo apt-get update, any clues on what might be causing this?
sudo apt-get update
Hit:1 http://linux.teamviewer.com/deb stable InRelease
Hit:2 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:3 https://brave-browser-apt-release.s3.brave.com stable InRelease
Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:5 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:6 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu bionic InRelease
Hit:7 http://packages.microsoft.com/repos/vscode stable InRelease
Hit:9 http://apt.postgresql.org/pub/repos/apt bionic-pgdg InRelease
Hit:8 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Err:10 http://br.archive.ubuntu.com/ubuntu bionic InRelease
Could not connect to br.archive.ubuntu.com:80 (200.236.31.4). - connect (113: No route to host)
Err:11 http://br.archive.ubuntu.com/ubuntu bionic-updates InRelease
Unable to connect to br.archive.ubuntu.com:http:
Err:12 http://br.archive.ubuntu.com/ubuntu bionic-backports InRelease
Unable to connect to br.archive.ubuntu.com:http:
Reading package lists... Done
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/bionic/InRelease Could not connect to br.archive.ubuntu.com:80 (200.236.31.4). - connect (113: No route to host)
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Unable to connect to br.archive.ubuntu.com:http:
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Unable to connect to br.archive.ubuntu.com:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.
The br archive server for ubuntu is throwing 504 errors right now, either wait or change the text http://br.archive.ubuntu.com/ubuntu in /etc/apt/sources.list to http://archive.ubuntu.com/ubuntu.

apt update error with ubuntu 18.10 cosmic version [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
Problem: impossible to execute 'apt-get update' (Ubuntu 18.10)
Ubuntu 18.10 cosmic end of life
I tried to upgrade my system version but i got the same error of apt-get update command
$ apt update
Ign:1 http://archive.ubuntu.com/ubuntu cosmic InRelease
Ign:2 http://security.ubuntu.com/ubuntu cosmic-security InRelease
Ign:3 http://archive.ubuntu.com/ubuntu cosmic-updates InRelease
Ign:4 http://archive.ubuntu.com/ubuntu cosmic-backports InRelease
Err:5 http://security.ubuntu.com/ubuntu cosmic-security Release
404 Not Found [IP: 91.189.88.173 80]
Err:6 http://archive.ubuntu.com/ubuntu cosmic Release
404 Not Found [IP: 91.189.88.31 80]
Err:7 http://archive.ubuntu.com/ubuntu cosmic-updates Release
404 Not Found [IP: 91.189.88.31 80]
Err:8 http://archive.ubuntu.com/ubuntu cosmic-backports Release
404 Not Found [IP: 91.189.88.31 80]
Reading package lists... Done
E: The repository 'http://security.ubuntu.com/ubuntu cosmic-security 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.
E: The repository 'http://archive.ubuntu.com/ubuntu cosmic 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.
E: The repository 'http://archive.ubuntu.com/ubuntu cosmic-updates 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.
E: The repository 'http://archive.ubuntu.com/ubuntu cosmic-backports 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.

Resources