Re: [atomic-devel] systemd broken in fedora 25 atomic

2016-11-28 Thread Vasiliy Tolstov
2016-11-28 20:27 GMT+03:00 Dusty Mabe : > I guess I don't know exactly what your problem is. Can you give a > reproducer starting with Fedora 24 atomic? Is your problem with the > artifacts generated by Fedora or are you using custom trees you have > built yourself? This is my custom trees. --

Re: [atomic-devel] systemd broken in fedora 25 atomic

2016-11-28 Thread Colin Walters
On Mon, Nov 28, 2016, at 10:00 AM, Vasiliy Tolstov wrote: > I found hack in pagure.io, and in post process script remove protected > tmp and protected home. After that all works fine. Yeah, we'll carry the hack until systemd upgrades. For reference, this is: https://github.com/systemd/systemd/is

Re: [atomic-devel] systemd broken in fedora 25 atomic

2016-11-28 Thread Dusty Mabe
On 11/28/2016 10:00 AM, Vasiliy Tolstov wrote: > 2016-11-28 17:55 GMT+03:00 Dusty Mabe : >> Hey Vasiliy. By default we use NetworkManager in Atomic Host. Are you >> enabling systemd-networkd? Can you share how your machine is set up? > > > I found hack in pagure.io, and in post process script r

Re: [atomic-devel] systemd broken in fedora 25 atomic

2016-11-28 Thread Vasiliy Tolstov
2016-11-28 17:55 GMT+03:00 Dusty Mabe : > Hey Vasiliy. By default we use NetworkManager in Atomic Host. Are you > enabling systemd-networkd? Can you share how your machine is set up? I found hack in pagure.io, and in post process script remove protected tmp and protected home. After that all work

Re: [atomic-devel] systemd broken in fedora 25 atomic

2016-11-28 Thread Dusty Mabe
On 11/25/2016 07:15 PM, Vasiliy Tolstov wrote: > I'm try to update my atomic host from fedora 24 to fedora 25. > And my network fails to up. Please see attached screenshot. > systemd-networkd.service: Failed at step NAMESPACE spawning > /usr/lib/systemd/systemd-networkd: Too many levels of symbol