Bug 1507616 - Error response from daemon: linux seccomp: Decoding seccomp profile failed: invalid character '<' after object key:value pair.
Summary: Error response from daemon: linux seccomp: Decoding seccomp profile failed: i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: docker
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-30 17:51 UTC by Micah Abbott
Modified: 2017-11-15 20:09 UTC (History)
13 users (show)

Fixed In Version: docker-1.13.1-40.git877b6df.fc26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-15 20:09:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Micah Abbott 2017-10-30 17:51:28 UTC
After rebasing to the 'fedora/26/x86_64/testing/atomic-host' branch on F26 Atomic Host, our automated tests are encountering the error message in the summary when trying to run Docker containers.

It looks like there were some 'diff' comments left in the '/etc/docker/seccomp.json' file; see below:


# rpm-ostree status
State: idle
Deployments:
● fedora-atomic:fedora/26/x86_64/testing/atomic-host
                   Version: 26.150 (2017-10-30 17:01:58)
                    Commit: 8ceb3dbf64fd39fed090b12aef68a78aafc7d2ca0161ba373806aa38ec73eaf4
              GPGSignature: Valid signature by E641850B77DF435378D1D7E2812A6B4B64DAB85D

# rpm -q docker
docker-1.13.1-36.git8fd0ebb.fc26.x86_64

# docker run --rm docker.io/busybox echo hello                               
/usr/bin/docker-current: Error response from daemon: linux seccomp: Decoding seccomp profile failed: invalid character '<' after object key:value pair.


# docker info | grep seccomp
 seccomp
  WARNING: You're not using the default seccomp profile
  Profile: /etc/docker/seccomp.json


# tail /etc/docker/seccomp.json 
                                ]
                        },
                        "excludes": {}
                }
        ]
<<<<<<< HEAD
}
=======
}
>>>>>>> 8c0a435... docker-2:1.13.1-35.git8fd0ebb

Comment 1 Fedora Update System 2017-11-03 20:17:39 UTC
atomic-1.19.1-6.fc26 docker-1.13.1-40.git877b6df.fc26 skopeo-0.1.24-7.gitdd2c3e3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cbf83e5281

Comment 2 Fedora Update System 2017-11-04 19:57:07 UTC
atomic-1.19.1-6.fc26, docker-1.13.1-40.git877b6df.fc26, skopeo-0.1.24-7.gitdd2c3e3.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cbf83e5281

Comment 3 Fedora Update System 2017-11-15 20:09:31 UTC
atomic-1.19.1-6.fc26, docker-1.13.1-40.git877b6df.fc26, skopeo-0.1.24-7.gitdd2c3e3.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.