podman-remote build: -v is a NOP

[edsantiago]

It does check for invalid path:

$ ../bin/podman-remote build -v /foo:/bar .
Error: error checking path "/foo": stat /foo: no such file or directory

...but apart from that, it seems to be a NOP. Rather than fill out a detailed issue with a custom-crafted Containerfile and logs, I'm going to take a step back and ask: what does -v mean in the context of podman-remote, anyway? I'm tempted to think it should be intercepted with a fatal you-seem-to-be-unclear-on-the-concept error.

[rhatdan]

Well it should be hidden.

[edsantiago]

I guess I should've included a setup:

$ cat Containerfile
FROM alpine
RUN mount | grep foo
$ mkdir /tmp/mymount
$ echo hi >/tmp/mymount/myfile
$ ../bin/podman-remote build -t foo -v /tmp/mymount:/foo .
STEP 1: FROM alpine
STEP 2: RUN mount | grep foo
Error: error building at STEP "RUN mount | grep foo": error while running runtime: exit status 1

With non-remote:

$ ../bin/podman build -t foo -v /tmp/mymount:/foo .
STEP 1: FROM alpine
STEP 2: RUN mount | grep foo
tmpfs on /foo type tmpfs (rw,seclabel,nosuid,nodev,nr_inodes=409600,inode64)
--> 5a6d0524e3c
STEP 3: RUN cat /foo/myfile
hi
STEP 4: COMMIT foo
--> 8131cb095fb
8131cb095fb56f67408e5b4e75083f07f740f9ac4554b25fdc87201a5aea2915

The way I read @Luap99's comments in #9882, I believe he's saying that -v /fs:/fs should work. It does not. Reopening.

[Luap99]

Yes it should work but I only tested with podman create/run and never podman build.

[github-actions]

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

[rhatdan]

This is now documented.