Comments

79 Comments

I can't run any containers with this update on a Fedora 26 Atomic Host.

# 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.

https://bugzilla.redhat.com/show_bug.cgi?id=1507616

This fixes bz#1500820 for me; the remaining functionality worked fine.

BZ#1500820 multiple 'systemd' AVC denials related to 'sysfs'

I saw some AVC denials on Fedora 26 Atomic Host when using this build.

https://bugzilla.redhat.com/show_bug.cgi?id=1500820

i concur about the legitimacy of this

BZ#1457912 /var/lib/docker mount does not persist across reboot.
karma

Fixes atomic #995 too

karma

This includes a fix for [atomic#995}(https://github.com/projectatomic/atomic/issues/995).

Worked for me! 👍

karma

Sorry to spoil the party, but I ran into this issue: atomic#995

karma

Sorry to spoil the party, but I ran into this issue: atomic#995

karma

Sorry to spoil the party, but I ran into this issue: atomic#995

karma

Sorry to spoil the party, but I ran into this issue: atomic#995

karma

This worked for me. It also fixed BZ#1437136

BZ#1434430 Confusing warning with 2nd start of container with atomic run

Worked for me on Dusty's custom F26AH image

BZ#1436777 F26AH is not using overlay storage driver by default

Worked OK for me on F26 Cloud Base

BZ#1437604 'container-storage-setup --reset' returns 'Info: command not found'
karma

atomic storage reset did not work for me - #1437604

Works well on x86_64

karma

works for me. passes sanity tests.