Skip to content

issue: docker.io in syntax= definitions does not work in corporate network #988

@georglauterbach

Description

@georglauterbach

Using a Dockerfile works in a corporate network because the syntax= definition is used correctly. But when using the image directive (because a build with a Dockerfile is not required), Dev Containers use a fallback

useBuildKitBuildContexts && !(imageBuildInfo.dockerfile && supportsBuildContexts(imageBuildInfo.dockerfile)) ? '# syntax=docker/dockerfile:1.4' :

that cannot be resolved properly in our network. Can we do something about this, or do I have to use a Dockerfile?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions