Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--quiet option not honored when building image with docker cli #12566

Closed
stac47 opened this issue Dec 10, 2021 · 1 comment · Fixed by #12571
Closed

--quiet option not honored when building image with docker cli #12566

stac47 opened this issue Dec 10, 2021 · 1 comment · Fixed by #12571
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@stac47
Copy link

stac47 commented Dec 10, 2021

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

/kind bug

Description

Running docker CLI against the podman service socket, the --quiet option for docker build is not honoured: in addition to the image ID, we have an additional line like Successfully built e49ef0b54fd7

Steps to reproduce the issue:

Comparing the three output (docker, docker against podman-service, podman --remote)

  1. Docker alone
% docker build -q - <<EOF
FROM fedora
RUN echo hello
EOF
sha256:f4ca4e453596279891a00e7c42d14eb01afd5cfae593e94f2765d4d8b6aead4f
  1. Docker with podman service
% ./bin/podman system service -t0&
% DOCKER_HOST=unix:///run/user/$UID/podman/podman.sock docker build -q - <<EOF
FROM fedora
RUN echo hello
EOF
e49ef0b54fd78fb2652d9a687db3b90385f50e0366baa27745dc6b48ae8d4c83
Successfully built e49ef0b54fd7
  1. Podman remote
% podman --remote build -q - <<EOF
FROM fedora
RUN echo hello
EOF
f9472b5bea3d3c081441bb5a97caa6080de28c71a7161fc539c4a0ae5ce21c26

Describe the results you received:

In the cases 1 and 3 the --quiet option is respected: we only get the built image ID. In case 2, an additional line Successfully built e49ef0b54fd7 is added.

Describe the results you expected:

Case 2 should be like cases 1 and 3.

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

Output of podman version:
This morning built but also occurs on podman 3.4.3 from fedora package.

% podman version
Version:      4.0.0-dev
API Version:  4.0.0-dev
Go Version:   go1.17.3
Git Commit:   1bfbb28b0365790552483b961b4bd48a69dd8070
Built:        Tue Nov 23 09:39:21 2021
OS/Arch:      linux/amd64

Output of podman info --debug:

host:                                                                                                                                                                                                                                                                  [77/288]
  arch: amd64
  buildahVersion: 1.23.1
  cgroupControllers:
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: 'conmon: /usr/bin/conmon'
    path: /usr/bin/conmon
    version: 'conmon version 2.0.25, commit: unknown'
  cpus: 8
  distribution:
    codename: impish
    distribution: ubuntu
    version: "21.10"
  eventLogger: journald
  hostname: lstacul-vm
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 165536
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 165536
      size: 65536
  kernel: 5.13.0-21-generic
  linkmode: dynamic
  logDriver: journald
  memFree: 1557430272
  memTotal: 16779907072                                                                                                                                                                                                                                                [39/288]
  networkBackend: cni
  ociRuntime:
    name: crun
    package: 'crun: /usr/bin/crun'
    path: /usr/bin/crun
    version: |-
      crun version 0.17
      commit: 0e9229ae34caaebcb86f1fde18de3acaf18c6d9a
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: 'slirp4netns: /usr/bin/slirp4netns'
    version: |-
      slirp4netns version 1.0.1
      commit: 6a7b16babc95b6a3056b33fb45b74a6f62262dd4
      libslirp: 4.4.0
  swapFree: 0
  swapTotal: 0
  uptime: 592h 25m 15.42s (Approximately 24.67 days)
plugins:
  log:
  - k8s-file
  - none
  - passthrough
  - journald                                                                                                                                                                                                                                                            [1/288]
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries: {}
store:
  configFile: /home/ubuntu/.config/containers/storage.conf
  containerStore:
    number: 7
    paused: 0
    running: 0
    stopped: 7
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /mnt/my-xfs/podman-user-root
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 297
  runRoot: /mnt/my-xfs/podman-user-root
  volumePath: /mnt/my-xfs/podman-user-root/volumes
version:
  APIVersion: 4.0.0-dev
  Built: 1637660361
  BuiltTime: Tue Nov 23 09:39:21 2021
  GitCommit: 1bfbb28b0365790552483b961b4bd48a69dd8070
  GoVersion: go1.17.3
  OsArch: linux/amd64
  Version: 4.0.0-dev

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

It occurs with dev HEAD but also with fedora 35 test package

podman-3.4.3-1.fc35.x86_64

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

Yes

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

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 10, 2021
@vrothberg
Copy link
Member

Thanks for reporting the issue, I'll take a look.

@vrothberg vrothberg self-assigned this Dec 10, 2021
vrothberg added a commit to vrothberg/libpod that referenced this issue Dec 13, 2021
Fixes: containers#12566
Signed-off-by: Valentin Rothberg <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants