podman-remote build: --rm=false is ignored

[edsantiago]

In window 1:

$ ./bin/podman system service --timeout=0

In window 2:

$ cat Dockerfile
FROM alpine
RUN date
RUN echo hello
RUN echo goodbye
$ ../bin/podman-remote build --force-rm=false --layers --rm=false -t foo .
STEP 1: FROM alpine
STEP 2: RUN date
Mon Mar 29 18:28:51 UTC 2021
--> b9328ccce3e
STEP 3: RUN echo hello
hello
--> f5b01f9cb4c
STEP 4: RUN echo goodbye
goodbye
STEP 5: COMMIT foo
--> 9a41527cdb1
9a41527cdb1dc71359791d4db8d5c542c1f4974b0341c3915ebd4b751d27577e
$ buildah containers
CONTAINER ID  BUILDER  IMAGE ID     IMAGE NAME                       CONTAINER NAME

That is: empty output from buildah containers. Expected multiple non-deleted layers:

$ buildah containers
CONTAINER ID  BUILDER  IMAGE ID     IMAGE NAME                       CONTAINER NAME
fa2db0a99cfd     *     302aba9ce190 docker.io/library/alpine:latest  alpine-working-container
5fb1c74a92a2     *     fa3e1b440db3                                  fa3e1b440db32af589c022c212375db64359d7381ed64380ab9f7b095e8b7380-working-container
fd7777c2756d     *     d9c3da18bc3e                                  d9c3da18bc3e5f3db3fcd183cf0d54fa109e136754335cc5c5df2211e6e78da9-working-container

[edsantiago]

I'm pretty confused. This is not fixed, even in 8c0df1c with buildah-v1.20.1-0.20210402144408-36a37402d0c8. And looking at #9884, I see:

        if options.RemoveIntermediateCtrs {
		params.Set("rm", "1")
	}

...but this issue relates to --rm=false, and I'm wondering if there's a default somewhere (I can't find it) such that the above is a NOP, and what we need is to override the default 1? Reopening.

[github-actions]

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

[edsantiago]

Still present in 54bed10