Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
atomic -h works well w/o docker daemon running on rhelah 7.2.5 now.
[cloud-user@atomic-00 ~]$ sudo atomic host status
TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC
* 2016-06-18 15:21:12 7.2.5 9bfe1fb650 rhel-atomic-host rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
[cloud-user@atomic-00 ~]$ sudo systemctl stop docker
[cloud-user@atomic-00 ~]$ sudo atomic -h | grep 'Atomic host'
host execute Atomic host commands
[cloud-user@atomic-00 ~]$ sudo atomic info -h
usage: atomic info [-h] [--remote] image
positional arguments:
image container image
optional arguments:
-h, --help show this help message and exit
--remote ignore local images and only scan registries
atomic info attempts to read and display the LABEL information about an image
Description of problem: Atomic -h/--help is a user layer help document, it doesn't depend on docker daemon running or not, so it needn't to connect /var/run/docker.sock. Version-Release number of selected component (if applicable): # rpm -q atomic atomic-1.9-4.gitff44c6a.el7.x86_64 How reproducible: always Steps to Reproduce: 1. strace -e trace=network atomic -h Actual results: # strace -e trace=network atomic -h --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=15204, si_status=0, si_utime=0, si_stime=0} --- --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=15206, si_status=0, si_utime=0, si_stime=0} --- socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 7 connect(7, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 7 connect(7, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=15208, si_status=0, si_utime=0, si_stime=0} --- socket(PF_LOCAL, SOCK_STREAM, 0) = 3 connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/docker.sock"}, 22) = -1 ENOENT (No such file or directory) <ignore/> Expected results: Additional info: it seems it also shouldn't connect /var/run/nscd/socket.