Skip to content

podman-remote: build: does not emit 'STEP' #7136

@edsantiago

Description

@edsantiago

Also, other output is out of order, and includes unexpected cruft.

In window 1:

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

In window 2:

$ printf "FROM alpine\nRUN echo hi\n" >Containerfile
$ ./bin/podman-remote build -t foo -f Containerfile .
hi               <----- what is this doing here? I expected it much farther down below
Getting image source signatures
Copying blob sha256:50644c29ef5a27c9a40c393a73ece2479de78325cae7d762ef3cdc19bf42dd0a
Copying blob sha256:1846819bbfecae935016434cedca6048bea8129532da628c1b5a88c29a77ea66
Copying config sha256:44c079bfdef6a5d51438995fa9dce6e70add2204c2d2dacfc0165e0379d9e650
Writing manifest to image destination
Storing signatures
--> 44c079bfdef
44c079bfdef6a5d51438995fa9dce6e70add2204c2d2dacfc0165e0379d9e650

FROM alpine          <--- expected: STEP 1
RUN echo hi          <--- expected: STEP 2
COMMIT foo           <--- expected: STEP 3
Successfully built 44c079bfdef6a5d51438995fa9dce6e70add2204c2d2dacfc0165e0379d9e650

Comparison against non-remote:

$ ./bin/podman build -t foo -f Containerfile .
STEP 1: FROM alpine
STEP 2: RUN echo hi
hi
STEP 3: COMMIT foo
--> fa3f90c1de0
fa3f90c1de0be86d636cc70d4ca5d817c9d2292f7cb52a681a0c27afdaf30c52

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.remoteProblem is in podman-remote

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions