Skip to content

Docker context should not be at root #2

@AndrewFasano

Description

@AndrewFasano

Containers currently pass the entire repo content as the context - this will slow things down.

Right now containers must be built from the root of the repo like this. The final dot is passing the entire repo as context

docker build -t dns320 -f ./d-link/dns320/Dockerfile.dns320 .

They should instead build with just the relevant context like

cd d-link/dns320
docker build -t dns320 -f Dockerfile.dns320 .

or

cd d-link/dns320
docker build -t dns320 -f ./d-link/dns320/Dockerfile.dns320 ./d-link/dns320/

The paths in the dockerfiles would then need to be updated to be relative to these directories e.g., https://github.com/rehosting/examples/blob/main/d-link/dns320/Dockerfile.dns320#L20

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions