--sig-proxy does not default to true when using -a, despite the docs

[SevereOverfl0w]

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

/kind bug

Description

podman-start when using -ai does not default to --sig-proxy=true, but this conflicts with the documentation in man podman-start

Steps to reproduce the issue:

1. podman start -ai 'SomeContainer'

2. Ctrl-C

Describe the results you received:

Pod is still running in the background

Describe the results you expected:

Pod is not running anymore

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

Output of podman version:

Version:      2.0.1
API Version:  1
Go Version:   go1.14.4
Built:        Thu Jan  1 01:00:00 1970
OS/Arch:      linux/amd64

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.15.0
  cgroupVersion: v1
  conmon:
    package: Unknown
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.17, commit: unknown'
  cpus: 8
  distribution:
    distribution: '"void"'
    version: unknown
  eventLogger: file
  hostname: ferule
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.6.19_1
  linkmode: dynamic
  memFree: 17856970752
  memTotal: 25121062912
  ociRuntime:
    name: runc
    package: Unknown
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.1-dev'
  os: linux
  remoteSocket:
    path: /run/user/1000/podman/podman.sock
  rootless: true
  slirp4netns:
    executable: /bin/slirp4netns
    package: Unknown
    version: |-
      slirp4netns version 1.0.1
      commit: 6a7b16babc95b6a3056b33fb45b74a6f62262dd4
      libslirp: 4.3.0
  swapFree: 8589930496
  swapTotal: 8589930496
  uptime: 3h 55m 29.79s (Approximately 0.12 days)
registries: {}
store:
  configFile: /home/overfl0w/.config/containers/storage.conf
  containerStore:
    number: 1
    paused: 0
    running: 0
    stopped: 1
  graphDriverName: vfs
  graphOptions: {}
  graphRoot: /home/overfl0w/.local/share/containers/storage
  graphStatus: {}
  imageStore:
    number: 2
  runRoot: /tmp/run-1000/containers
  volumePath: /home/overfl0w/.local/share/containers/storage/volumes
version:
  APIVersion: 1
  Built: 0
  BuiltTime: Thu Jan  1 01:00:00 1970
  GitCommit: ""
  GoVersion: go1.14.4
  OsArch: linux/amd64
  Version: 2.0.1

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

❯ pacinfo podman     
architecture: x86_64
filename-sha256: 0f7c9029a9f3dc1f09574694d01f2e9b3677d5f7f31f36ba403e76685e8a2e5f
filename-size: 22MB
homepage: https://podman.io/
installed_size: 52MB
license: Apache-2.0
maintainer: Cameron Nemo <[email protected]>
pkgname: podman
pkgver: podman-2.0.1_1
repository: https://alpha.de.repo.voidlinux.org/current
run_depends:
	runc>=0
	conmon>=0
	cni-plugins>=0
	slirp4netns>=0
	containers.image>=0
	glibc>=2.29_1
	libgpgme>=1.12.0_2
	libassuan>=2.0.1_1
	libgpg-error>=1.6_1
	libseccomp>=2.0.0_1
	device-mapper>=2.02.110_1
shlib-requires:
	libpthread.so.0
	libgpgme.so.11
	libassuan.so.0
	libgpg-error.so.0
	libseccomp.so.2
	librt.so.1
	libdevmapper.so.1.02
	libc.so.6
short_desc: Simple management tool for containers and images
source-revisions: podman:2994737a5a

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

[mheon]

Probably a symptom of the 2.0 CLI migration. I'll take this.

[SevereOverfl0w]

This wasn't a problem for me in the 1.0 series, I should have mentioned that, sorry.