Error on container rebuild and reopen: failed to fetch from ubuntu archive
Nobody has claimed this yet.
- #21 by @riccardobattiato — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- docker
- Domain
- build-system, devops
Research direction
Start by reproducing the failure with VS Code's “Dev Containers: Rebuild and Reopen in Container” command and inspect the build logs around the Ubuntu archive fetch. The issue names no configuration file or test; done means the image builds and the development environment opens successfully.
Written by the indexing model from the issue text.
Description
Describe the bug
Following tutorial instructions: Dev Containers Rebuild and Reopen in Container will fail due to error:
Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/d/dash/dash_ 0.5.10.2-6_amd64.deb 403 connecting to archive.ubuntu.com:80: connecting to 91 .189.91.82:80: dial tcp 91.189.91.82:80: connectex: Impossibile stabilire la con nessione. Risposta non corretta della parte connessa dopo l'intervallo di tempo oppure mancata risposta dall'host collegato. [IP: 91.189.91.82 80] 85.86 E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
To Reproduce
Steps to reproduce the behavior:
- Clone repo
- In VS Code, open the command palette with
Ctrl / Cmd + Shift + P. Then, enter and runDev Containers: Rebuild and Reopen in Container - Wait for process to interrupt
- Read logs and see the error
Expected behavior
The image should build and the dev environment should open successfully
Desktop (please complete the following information):
- Windows 11 Pro
- Version 22H2
- Docker 4.26.1 (131620)
- Dominant language
- Dockerfile
- Stars
- 177
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from freeCodeCamp/rdb-alpha
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
freeCodeCamp/rdb-alpha#103 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
freeCodeCamp/rdb-alpha#31 · 3 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
freeCodeCamp/rdb-alpha#25 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
freeCodeCamp/rdb-alpha#19 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
freeCodeCamp/rdb-alpha#15 · 1 comment ·
All issues in freeCodeCamp/rdb-alpha
Similar issues
-
mock-core-configs/etc/mock/rocky-10-riscv64.cfg contains the wrong architecture in config_opts['root']Possibly taken @jasonmontleon claimed this 4 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 94/100
rpm-software-management/mock#1834 ·
-
status:in-linear
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
n8n-io/n8n#43006 · 3 comments ·
Maintainers usually reply within 1 day
-
is:build
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
leanprover-community/lean4game#589 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
unocss/unocss#5421 · 1 comment ·
Maintainers usually reply within 1 day