sdk image cannot be used in devcontainers

Open

#93 opened on Mar 10, 2024 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: docker, vscode
Domain: devops

Research direction

Start with the reproduction using ghcr.io/wolfi-dev/sdk:latest, then run the linked VS Code check-requirements-linux.sh script in the container and confirm the missing libstdc++.so.6 requirement. Trace how the SDK image is built from the repository's image or package definitions, and consider the issue done when the check succeeds and the image can start as a VS Code devcontainer.

Written by the indexing model from the issue text.

Description

enhancement needs-triage

Description

Go to vscode and start a devcontainer of wolfi-dev/os

[22577 ms] Start: Run in container: test -x '/root/.vscode-server-insiders/bin/6c19c003574b02afc604c0c1c471b1441b33a3d3-insider/bin/helpers/check-requirements.sh'
[22579 ms] 
[22579 ms] 
[22579 ms] Start: Run in container: '/root/.vscode-server-insiders/bin/6c19c003574b02afc604c0c1c471b1441b33a3d3-insider/bin/helpers/check-requirements.sh'
[22584 ms] 
[22584 ms] 
[22584 ms] Exit code 1
[22584 ms] Start: Run: docker rm -f 499089790db940e06e2d7cbd79abf2939dffe31c2ed39ef59dbe349486d92beb
[22587 ms] Command in container failed: '/root/.vscode-server-insiders/bin/6c19c003574b02afc604c0c1c471b1441b33a3d3-insider/bin/helpers/check-requirements.sh'
[22587 ms] Exit code 1
[22723 ms] Container server terminated (code: 137, signal: null).

for easier reproducing the issue,

docker run --rm -it ghcr.io/wolfi-dev/sdk:latest
curl -o test.sh https://raw.githubusercontent.com/microsoft/vscode/main/resources/server/bin/helpers/check-requirements-linux.sh
sh test.sh
echo $?

It seems to fail as it cannot find libstdc++.so.6 as requirement

Dominant language: HCL
Stars: 28
Forks: 25
Avg merge: 4d 31m
Merged PRs (30d): 6

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Open

area: ci bug perceived difficulty: 3

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment · Opened Sep 22, 2026
Usage controller writes the in-use label on every reconcile even though it is already set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

crossplane/crossplane#7859 · Opened Sep 22, 2026
[Bug]: avm-ptn-alz-connectivity-hub-and-spoke-vnet builds vpnClientRevokedCertificates without the properties wrapper Open

Product: Terraform (AVM) Topic: Networking (HS) :globe_with_meridians:

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

Azure/Azure-Landing-Zones#4282 · 1 comment · Opened Sep 22, 2026
[BUG] update base image to ubuntu resolute Open

Difficulty 1/5 Under an hour Newbie friendliness 88/100

linuxserver/docker-code-server#222 · Opened Sep 22, 2026
[BUG] Package template mutation when constructing Apps during update retries Open

bug carvel-triage

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

carvel-dev/kapp-controller#1861 · Opened Sep 22, 2026

More DevOps issues