On Sun, Sep 29, 2019 at 02:15:19AM +0800, 沙包妖梦 wrote:
> Hello, and help, I ran into an issue for several times. I don't know when
> and why it happen.
>
> When I want to restart some service, it sais: "Failed to start
> xx.service: Unit .mount is masked".
> .mount has
Hello, and help, I ran into an issue for several times. I don't know when
and why it happen.
When I want to restart some service, it sais: "Failed to start
xx.service: Unit .mount is masked".
.mount has "RequiresMountsFor" or "PrivateTmp".
When this happens, I will see ALL mountpoint
Two things :
1) I used the following on the host (you noted I do not need
systemd-networkd on the host)
# dnf install systemd-networkd
==>
No match for argument: systemd-networkd
Error: Unable to find a match: systemd-networkd
2) To create the container (feedback welcome) I used :
//
export
On Sat, 2019-09-28 at 10:03 -0600, Douglas E. Hopley Jr. wrote:
> I get the error when, on the host, I am creating the container.
> To this point, I have found my setups work needing systemd-networkd on both
> the host and container.
>
> The distro for the container I am working to set
Hmm that's odd, Fedora should have systemd-networkd by default, and you
shouldn't need it on the host (I've used networkd on the container end
before but always use NetworkManager on my host system.) What command
*exactly* gave the error that networkd wasn't found?
On Sat, Sep 28, 2019, 11:03 AM
I get the error when, on the host, I am creating the container.
To this point, I have found my setups work needing systemd-networkd on
both the host and container.
The distro for the container I am working to set up is 'Fedora 30 '.
That is also
the host distro too. Seems I have something
On Fri, 2019-09-27 at 17:12 +0200, Mirza Krak wrote:
> This is what the systemd-growfs@.service looks like:
>
> # Automatically generated by systemd-fstab-generator
> [Unit]
> Description=Grow File System on %f
> Documentation=man:systemd-growfs@.service(8)
> DefaultDependencies=no
>
