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.
Bug 1451016 - unable to configure the Docker daemon due to missing /etc/docker/daemon.json: [ENOENT]
Summary: unable to configure the Docker daemon due to missing /etc/docker/daemon.json:...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhel7-container-engine-docker
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Jhon Honce
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On: 1451375
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-15 14:54 UTC by Ed Santiago
Modified: 2021-01-15 07:35 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:35:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ed Santiago 2017-05-15 14:54:51 UTC 
I hope this is the right component for this. 'systemctl start docker' fails because of missing /etc/docker/daemon.json :

    May 15 14:47:22 esm-rhelah73-1.localdomain runc[13728]: time="2017-05-15T14:47:22Z" level=fatal msg="unable to configure the Docker daemon with file /etc/docker/daemon.json: open /etc/docker/daemon.json: no such file or directory\n"

    # atomic images list
       REPOSITORY                                                                    TAG      IMAGE ID       CREATED            VIRTUAL SIZE   TYPE      
       brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7/container-engine   latest   abe2a60f2d1a   2017-05-15 14:45                  ostree    


Workaround:

    # echo '{}' >/etc/docker/daemon.json
    # systemctl start docker
    ...all ok

I suspect this needs to be handled in the system container packaging, but I have no actual clue how that works.
Comment 2 Jhon Honce 2017-05-15 17:59:58 UTC 
This should have been fixed as of rhel7-container-engine-docker-1.12-6 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=557100
Comment 3 Ed Santiago 2017-05-15 18:19:17 UTC 
That's the one I'm reporting:

    # atomic images version brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7/container-engine:latest
    IMAGE NAME                                                                                  VERSION   IMAGE ID  
    brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7/container-engine:latest          1.12-6    abe2a60f2d1a
Comment 4 Steve Milner 2017-05-15 19:00:56 UTC 
To double check I pulled the latest from brew and installed it with atomic (checkout from git) and it worked. I'm wondering if the file copy feature has not landed in RHEL yet.

Ed,

What version of atomic did you use and what arguments did you use to install the system container?


Giuseppe,

Could this be related to an old version of atomic that doesn't copy files to the host?
Comment 5 Ed Santiago 2017-05-15 19:49:03 UTC 
    # rpm -q atomic
    atomic-1.16.5-1.el7.x86_64

    # atomic --version
    1.16.5

    # atomic host status
    State: idle
    Deployments:
    ● rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
                 Version: 7.3.4-1 (2017-04-20 22:00:30)
                  Commit: d6c7a5639cdeb6c21cf40d80259d516d047176e35411c8684cae40a93eedbed0
                  OSName: rhel-atomic-host
Comment 6 Steve Milner 2017-05-15 20:07:58 UTC 
The feature we are using was merged after the 1.16.5 release.

(NEWER)
commit 430961af37b26efd6df7334474a4ed76915746be
Author: Giuseppe Scrivano <gscrivan>
Date:   Fri Nov 25 12:04:22 2016 +0100

    syscontainers: allow to copy arbitrary files to the host
    
    Copy the /exports/hostfs/ to the host file system.
<snip>
commit 241adc115aa6e7975e180c3d97e2e6be4bf38325
Author: Daniel J Walsh <dwalsh>
Date:   Tue Mar 21 15:05:34 2017 -0400

    Bump to v1.16.5
(OLDER)


The oldest release that the copy feature is part of is 1.17.0:

commit 5378d20c0308af63745ec1ec52e8de684daaf927
Author: Daniel J Walsh <dwalsh>
Date:   Thu Apr 20 11:45:50 2017 -0400


There are a number of ways I can see fixing this:

1. Make a later version of atomic available for the distribution
2. Require the user to create an /etc/docker/daemon.json file (docs and set in tag)
3. Backport the feature to 1.16.5 (least favorite by far)

Adding NEEDINFO on Giuseppe as I feel like he'll have good insight.
Comment 7 Giuseppe Scrivano 2017-05-16 07:35:25 UTC 
yes this depends on a newer feature of atomic that is not in RHEL yet.  Adding Dan to check what is the best way to address this.  I guess it might be easier to cut a new atomic release.
Comment 8 Daniel Walsh 2017-05-16 12:28:22 UTC 
Yes we should cut a new atomic release.  Brent was planning on doing this.
Comment 9 Steve Milner 2017-05-22 15:13:29 UTC 
I believe this should be re-testable at this point.
Comment 15 RHEL Program Management 2021-01-15 07:35:59 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.