I am trying to configure a container after creation using machinectl
but I'm coming up against problems in my implementation. If this
isn't the correct way to set up a container after creation please let
me know the right way.
-My Implementation--
I'm running a bash loop installing
I have a few gigs - so it shouldn't be a problem. I'm using parallels
9. I will try manually when I have the time.
On Tue, Jun 23, 2015 at 2:18 PM, Johannes Ernst
johannes.er...@gmail.com wrote:
On Jun 23, 2015, at 7:45, Matthew Karas mkarasc...@gmail.com wrote:
I am trying to configure
I'm trying to use systemd-nspawn but when I launch it and try to login
as root - it still asks for a password and I can't seem to set one.
The docs for fedora mentioned turning off auditing - which I've done.
My cmd line says audit=0 at the end.
$ cat /proc/cmdline
Here is my output
https://gist.github.com/mkcybi/eae6a2a67c5dc864
-- Forwarded message --
From: Lennart Poettering lenn...@poettering.net
Date: Mon, Jun 15, 2015 at 11:32 AM
Subject: Re: [systemd-devel] Fedora 21 and systemd-nspawn
To: Matthew Karas mkarasc...@gmail.com
Cc
within 1s to kill container.
Failed to create directory /srv/srv1//sys/fs/selinux: Read-only file system
Failed to create directory /srv/srv1//sys/fs/selinux: Read-only file system
On Mon, Jun 15, 2015 at 12:24 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 15.06.15 12:21, Matthew Karas
service without my special configs (as it starts
dropbear.service). If I don't start dropbear.socket - my script
errors out because port22 isn't a socket.
On Mon, Jun 1, 2015 at 11:37 PM, Andrei Borzenkov arvidj...@gmail.com wrote:
В Mon, 1 Jun 2015 16:36:38 -0400
Matthew Karas mkarasc...@gmail.com
I am trying to start a dropbear service after my openvpn service starts up.
---
[Unit]
Description=SSH Per-Connection Server
Wants=dropbearkey.service
After=syslog.target dropbearkey.service
Wants=openvpn@equipment.service
After=openvpn@equipment.service
