On 5/19/17, Juan Hernández <jhern...@redhat.com> wrote:
> Did that restart of the docker daemon resolve the problem?
> As far as I can tell that 'RUN sed' instruction that failed is correct.
> I just re-checked it in my environment and it works correctly. Looks
> more like a resources issue or a bug in docker itself. The message says
> OOM, out of memory, is that machine low on memory maybe?

Restart of the docker daemon does not solve the issue. Will try to see
how the memory issue can be solved, since I have enough memory (8GB),
so the problem is not hardware.

- Warm regards
Leni Kadali Mutungi
Users mailing list

Reply via email to