Re: [systemd-devel] nspawn and mariadb /run/mysql

2020-06-17 Thread Damian Ivanov
Hello Lennart, Thanks for the answer. I will report this in the SUSE issue tracker than. A workaround I found for me is to create the structure like this: CONTAINER/root/ CONTAINER/run/mysql CONTAINER/run/passenger CONTAINER/run/obs and use -bind="" option for the problematic run dirs, where

Re: [systemd-devel] nspawn and mariadb /run/mysql

2020-06-16 Thread Lennart Poettering
On Di, 21.04.20 10:40, Damian Ivanov (damianator...@gmail.com) wrote: > Hi, > > After bootstrapping os and mariadb into $DIR > I booted the machine with: > systemd-nspawn -D $DIR -b --resolv-conf=bind-host --capability=all > I had to remove $DIR/etc/resolv.conf first as bind-host seems to fail

[systemd-devel] nspawn and mariadb /run/mysql

2020-04-21 Thread Damian Ivanov
Hi, After bootstrapping os and mariadb into $DIR I booted the machine with: systemd-nspawn -D $DIR -b --resolv-conf=bind-host --capability=all I had to remove $DIR/etc/resolv.conf first as bind-host seems to fail if $DIR/etc/resolv.conf already exists. mariadb.service was failing, after