Skip to content

Why not be explicit in "compose.yaml" about building Dockerfile? #820

@igorbga

Description

@igorbga

When we do the build Docker Compose tries to find an image called "app-php" in your local registry, then in Docker Hub and then if it doesn't find it, it resorts to using the provided Dockerfile.

If there was an image called "app-php" in Docker Hub or any other registry you might have configured, then this other image would have been downloaded and used instead of building the expected one.

Isn't this a security risk ?

Wouldn't it make more sense just being explicit and adding something like:

    build:
      context: .
      dockerfile: Dockerfile

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy