COPY --link not supported in Containerfile

[sanmai-NL]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Docker Engine incompatibility. Added with Dockerfile 1.4.
See: https://docs.docker.com/engine/reference/builder/#copy---link

‼️ This has a major efficiency impact.

Description

I want to use this feature, not being able to use the feature harms CI times as well as local development times when large data copying is interspersed with RUN commands.

Steps to reproduce the issue:

1. Create Containerfile:

# syntax=docker/dockerfile:1
FROM alpine:3.16
COPY \
  --link \
  Containerfile \
  /root/

3. Run podman buildx build .

Describe the results you received:

STEP 1/2: FROM alpine:3.16
Resolved "alpine" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull docker.io/library/alpine:3.16...
Getting image source signatures
Copying blob sha256:ca7dd9ec2225f2385955c43b2379305acd51543c28cf1d4e94522b3d94cce3ce
Copying config sha256:bfe296a525011f7eb76075d688c681ca4feaad5afe3b142b36e30f1a171dc99a
Writing manifest to image destination
Storing signatures
STEP 2/2: COPY   --link   Containerfile   /root/
Error: building at STEP "COPY --link Containerfile /root/": COPY only supports the --chmod=<permissions> --chown=<uid:gid> and the --from=<image|stage> flags

Describe the results you expected:

Container image built.

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Client:       Podman Engine
Version:      4.3.1
API Version:  4.3.1
Go Version:   go1.18.8
Built:        Wed Nov  9 21:43:58 2022
OS/Arch:      darwin/amd64

Server:       Podman Engine
Version:      4.3.0
API Version:  4.3.0
Go Version:   go1.19.2
Built:        Fri Oct 21 10:09:51 2022
OS/Arch:      linux/amd64

Output of podman info:

Not applicable.

Package info (e.g. output of rpm -q podman or apt list podman or brew info podman):

Not applicable.

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes/No

Additional environment details (AWS, VirtualBox, physical, etc.):

[flouthoc]

Hi @sanmai-NL , Thanks for creating the issue. This looks like duplicate of #4325, could you please track #4325.

I'm closing this issue but please feel free to re-open.

[sanmai-NL]

I'm a bit frustrated to have sought for open issues, and you point to buildah's project, which is a different tool from a user's viewpoint.

[flouthoc]

@sanmai-NL ah I am sorry for inconvenience, podman just uses buildah under-the-hood and we try to track build RFE there. But I understand that from user's perspective its just podman build.

[sanmai-NL]

In that sense, is any integration work needed after completing the feature in Buildah? Then this issue should be left open, no?

I read about the integration between Podman and Buildah ... in the Buildah README. Can you clarify the places where to report issues in the issue template? No need to apologize, just hope to save future contributors time.

[flouthoc]

Features from buildah are automatically vendor-ed into podman on every new release usually folks just comment on buildah tickets requesting to cut a release.

[rhatdan]

@flouthoc you can simply transfer the issue to buildah, no reason to close and recreate the issue.

[flouthoc]

@rhatdan There is already a similar issue here: #4325

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

Closing since we should work with the existing issue #4325