target.dockerfile: Mention that this path is relative to the context provided

[vishalnandagopal]

Is this a docs issue?

• My issue is about the documentation content or website

Type of issue

Other

Description

It's not clear that the path we provide here is relative to the context attribute, if provided. This caused some trouble since the build was failing without a clear reason, and was only evident by seeing the path again in the error.

Eg:

target "default" {
  dockerfile = "app/src/www/Dockerfile"
  context = "app"
}

Location

https://docs.docker.com/build/bake/reference/#targetdockerfile

Suggestion

The error was something like app/app does not exist so I thought the dockerfile was relative to the context. It would be useful if this was explicitly mentioned.

In general, now that bake is GA, it needs a much more beginner (me) friendly docs. Other things that were not clear and seemed unnecessary include - Default group is compulsory if multiple targets are present. This was not at all clear from the error message.

[docker-robot]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[vishalnandagopal]

/remove-lifecycle stale

[polarathene]

It is handled the same as Docker Compose build section. context is a prefix to dockerfile (unless an absolute path).

Presently Docker Compose differs from Docker Bake with context, with it's own relative path prefix being relative to the compose file (Docker Compose), or relative from the current working directory (Docker Bake).