Re: [atomic-devel] F21 Atomic broken for docker --memory

[Dusty Mabe <dusty dustymabe com>]

On Sun, Feb 01, 2015 at 12:28:47AM -0500, Dusty Mabe wrote:
> 
> It looks like latest F21 atomic tree (153f577dc4) is broken because of 
> an issue with systemd. Here is what I get:
> 
> -bash-4.3# docker run --rm --memory 500M busybox echo "I'm Alive"
> FATA[0003] Error response from daemon: Cannot start container d79629bfddc7833497b612e2b6d4cc2542ce9a8c2253d39ace4434bbd385185b: write /sys/fs/cgroup/memory/system.slice/docker-d79629bfddc7833497b612e2b6d4cc2542ce9a8c2253d39ace4434bbd385185b.scope/memory.memsw.limit_in_bytes: invalid argument
> 
> Looks like some others have hit this at [1]. I have typed up how to use
> atomic to reproduce the problem at [2]. It might work with systemd-218
> (in rawhide) but I haven't had a chance to test that.
> 
> Dusty
> 
> [1] - https://github.com/docker/docker/issues/10280 
> [2] - http://dustymabe.com/2015/01/31/crisis-averted-im-using-atomic-host/

Opened a bug to track. It has been fixed but will take a while to
trickle down:

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