podman: After podman machine start, periodic "connect: operation timed out" messages appear in the executing window.

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

/kind bug

Description

When I do

podman machine init
podman machine start

Everything works fine. However in the window where I executed those commands, I periodically get messages of the form ERRO[0168] net.Dial() = dial tcp 140.211.169.196:443: connect: operation timed out. These messages do not affect Podmans’ normal operation, but they do seem weird enough that I don’t know if they may indicate an underlying bug.

Steps to reproduce the issue:

In a terminal window:

1. podman machine init

2. podman machine start

Then wait for a minute or two for the first message to start appearing.

Describe the results you received:

Describe the results you expected:

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

Output of podman version:

podman version 3.4.1

Output of podman info --debug:

einan-mac:ocean-developer-tools einan$ podman info --debug host: arch: amd64 buildahVersion: 1.23.1 cgroupControllers: [] cgroupManager: systemd cgroupVersion: v2 conmon: package: conmon-2.0.30-2.fc34.x86_64 path: /usr/bin/conmon version: 'conmon version 2.0.30, commit: ’ cpus: 4 distribution: distribution: fedora variant: coreos version: “34” eventLogger: journald hostname: localhost 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.14.11-200.fc34.x86_64 linkmode: dynamic logDriver: k8s-file memFree: 2783457280 memTotal: 4104060928 ociRuntime: name: crun package: crun-1.2-1.fc34.x86_64 path: /usr/bin/crun version: |- crun version 1.2 commit: 4f6c8e0583c679bfee6a899c05ac6b916022561b spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +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: true serviceIsRemote: true slirp4netns: executable: /usr/bin/slirp4netns package: slirp4netns-1.1.12-2.fc34.x86_64 version: |- slirp4netns version 1.1.12 commit: 7a104a101aa3278a2152351a082a6df71f57c9a3 libslirp: 4.4.0 SLIRP_CONFIG_VERSION_MAX: 3 libseccomp: 2.5.0 swapFree: 0 swapTotal: 0 uptime: 12m 42.18s plugins: log:

• k8s-file
• none
• journald network:
• bridge
• macvlan volume:
• local registries: search:
• docker.io store: configFile: /var/home/core/.config/containers/storage.conf containerStore: number: 0 paused: 0 running: 0 stopped: 0 graphDriverName: overlay graphOptions: {} graphRoot: /var/home/core/.local/share/containers/storage graphStatus: Backing Filesystem: xfs Native Overlay Diff: “true” Supports d_type: “true” Using metacopy: “false” imageStore: number: 0 runRoot: /run/user/1000/containers volumePath: /var/home/core/.local/share/containers/storage/volumes version: APIVersion: 3.4.0 Built: 1633030821 BuiltTime: Thu Sep 30 19:40:21 2021 GitCommit: “” GoVersion: go1.16.8 OsArch: linux/amd64 Version: 3.4.0

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

einan-mac:ocean-developer-tools einan$ brew info podman
podman: stable 3.4.1 (bottled), HEAD
Tool for managing OCI containers and pods
https://podman.io/
/usr/local/Cellar/podman/3.4.1 (170 files, 39.5MB) *
  Poured from bottle on 2021-10-28 at 10:00:50
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/podman.rb
License: Apache-2.0
==> Dependencies
Build: go ✘, go-md2man ✘
Required: qemu ✔
==> Options
--HEAD
	Install HEAD version
==> Caveats
Bash completion has been installed to:
  /usr/local/etc/bash_completion.d
==> Analytics
install: 16,611 (30 days), 31,175 (90 days), 58,729 (365 days)
install-on-request: 16,614 (30 days), 31,178 (90 days), 58,652 (365 days)
build-error: 0 (30 days)

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.):

I am on Mac OS Big Sur.