microsoft / microsoft/vscode-containers

Add autocomplete for other registries

Open
#67 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

registries
Dominant language
TypeScript
Stars
139
Forks
87
Avg merge
9h 15m
Merged PRs (30d)
9

Description

It seems that images from hub.docker.com are the only ones that supports autocomplete inside Dockerfile.
I'd be nice if other registries are included, too.

Examples

hub.docker.com

Image

Other registries
Quay.io

Link: https://quay.io/quarkus/ubi9-quarkus-micro-image:2.0, which redirects to https://quay.io/repository/quarkus/ubi9-quarkus-micro-image?tab=tags&tag=2.0

Image

redhat.com

Catalog: https://catalog.redhat.com/software/containers/ubi9/openjdk-21/6501cdb5c34ae048c44f7814

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No implementation file or test is named. Start by locating the Dockerfile autocomplete entry point and how registry image references are handled; compare the existing hub.docker.com behavior with the Quay.io and Red Hat examples. Done means autocomplete also works for images from those registries.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript, vscode
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.