podman varlink printing errors

[johanbrandhorst]

/kind bug

Description

I started a local podman socket as suggested in #4076 (comment) and everything seems to be working just fine, however, I'm seeing a lot of errors printed from the podman "server".

$ podman varlink unix:/home/$(whoami)/podman.socket -t0
ERRO[0012] unable to find flag trace                    
ERRO[0012] unable to find flag authfile                 
ERRO[0012] unable to find flag cgroupns                 
ERRO[0012] unable to find flag env-host                 
ERRO[0012] unable to find flag cgroupns                 
ERRO[0012] unable to find flag http-proxy               
ERRO[0012] unable to find flag syslog                   
ERRO[0177] unable to find flag trace                    
ERRO[0177] unable to find flag authfile                 
ERRO[0177] unable to find flag cgroupns                 
ERRO[0177] unable to find flag env-host                 
ERRO[0177] unable to find flag cgroupns                 
ERRO[0177] unable to find flag http-proxy               
ERRO[0177] unable to find flag syslog

(It seems to happen every time a container is started).

Steps to reproduce the issue:

1. Start hosting podman

   $ podman varlink unix:/home/$(whoami)/podman.socket -t0

2. Start and run some containers over the varlink interface
3. Observe errors printed in podman log

Describe the results you received:

I saw a lot of errors logged.

Describe the results you expected:

No error logs.

Output of podman version:

$ podman version
Version:            1.5.1
RemoteAPI Version:  1
Go Version:         go1.12.8
OS/Arch:            linux/amd64

Output of podman info --debug:

$ podman info --debug
debug:
  compiler: gc
  git commit: ""
  go version: go1.12.8
  podman version: 1.5.1
host:
  BuildahVersion: 1.10.1
  Conmon:
    package: Unknown
    path: /usr/bin/conmon
    version: 'conmon version 2.0.0, commit: e217fdff82e0b1a6184a28c43043a4065083407f'
  Distribution:
    distribution: manjaro
    version: unknown
  MemFree: 1163882496
  MemTotal: 16569856000
  OCIRuntime:
    package: Unknown
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc8
      commit: 425e105d5a03fabd737a126ad93d62a9eeede87f
      spec: 1.0.1-dev
  SwapFree: 16968802304
  SwapTotal: 18223570944
  arch: amd64
  cpus: 8
  eventlogger: file
  hostname: REDACTED-x1
  kernel: 4.19.69-1-MANJARO
  os: linux
  rootless: true
  uptime: 213h 20m 53.58s (Approximately 8.88 days)
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ConfigFile: /home/REDACTED/.config/containers/storage.conf
  ContainerStore:
    number: 1
  GraphDriverName: vfs
  GraphOptions: null
  GraphRoot: /home/REDACTED/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 118
  RunRoot: /run/user/1000
  VolumePath: /home/REDACTED/.local/share/containers/storage/volumes

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

$ pacman -Qs podman
local/podman 1.5.1-1
    Tool and library for running OCI-based containers in pods
local/podman-docker 1.5.1-1
    Emulate Docker CLI using podman

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

Running on laptop directly.

[baude]

this is fixed upstream ... and will be part of the 1.6 release. re-open then if you see any more problems. thanks for the report.