[build] Incompatibility between end-of-command PATH and target relatively a Dockerfile with -f

未关闭
#7,309 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, go
领域
cli, documentation

调研方向

首先分别使用 legacy builder 和 BuildKit 重现 docker build -f Dockerfile subdirectory，然后检查 docker build 文档和 manpage 中关于 PATH 及 Dockerfile 位置的措辞。命令按描述正常工作，或者文档明确说明限制和正确用法，即视为完成。

由索引模型根据 Issue 内容生成。

描述

kind/bug status/0-triage
Description

docker build allows to provide a PATH at the end of the command to locate the Dockerfile there, or to target a Dockerfile with - f.

Reading at the documentation/manpage, it leads to think PATH becomes the working directory, and as such if we combine both we could use -f to target the Dockerfile relatively to PATH.

Reproduce

Picture this structure:

repo_root
|___subdirectory
       |____Dockerfile

One would expect here that we could be at repo_root and run docker build -f Dockerfile subdirectory as Dockerfile is at current location (.) when starting from subdirectory.

That's what lead to think the manpage.

The result however is this: ERROR: failed to build: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory

Note that although the error message is different, the issue exist for both legacy builder and BuildKit.

Expected behavior

The example given above should work, or if it's expected that it doesn't, the manpage might need a little rewording.

docker version

What's provided in GitHub Actions context first, then reproduced on an ArchLinux computer I don't have at hand to paste the block. Docker 29.8.0 on Arch (https://archlinux.org/packages/extra/x86_64/docker/) reproduced with legacy builder and BuildKit one (https://archlinux.org/packages/extra/x86_64/docker-buildx/)

docker info

Same as above, don't need to have the build running anyway.

Additional Info

No response

主要语言
Go
星标
6.1k
派生
2.2k
平均合并
1 天 15 小时
30 天内合并 PR
43

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

docker/cli 的其他 Issue

查看 docker/cli 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。