Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

systemd-nspawn --link-journal=host only works once #2186

Closed
smurfix opened this issue Dec 17, 2015 · 1 comment
Closed

systemd-nspawn --link-journal=host only works once #2186

smurfix opened this issue Dec 17, 2015 · 1 comment
Labels
bug 🐛 Programming errors, that need preferential fixing nspawn
Milestone

Comments

@smurfix
Copy link

smurfix commented Dec 17, 2015

systemd-nspawn --link-journal=host should accept an existing directory.

root@iron:~# systemctl start systemd-nspawn@foo
[ everything works ]
root@iron:~# systemctl stop systemd-nspawn@foo
root@iron:~# systemctl start systemd-nspawn@foo
[ fails ]
root@iron:~# systemctl status -l systemd-nspawn@foo
● systemd-nspawn@foo.service - Container foo
   Loaded: loaded (/lib/systemd/system/systemd-nspawn@.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/systemd-nspawn@.service.d
           └─smurf.conf
   Active: failed (Result: exit-code) since Do 2015-12-17 13:00:33 CET; 7s ago
     Docs: man:systemd-nspawn(1)
  Process: 12750 ExecStart=/usr/bin/systemd-nspawn --quiet --network-bridge=br0 --network-veth-extra=vb-%i:host443 --keep-unit --boot --link-journal=host --directory=/d/vm/%i --bind=/var/cache (code=exited, status=1/FAILURE)
 Main PID: 12750 (code=exited, status=1/FAILURE)
   Status: "Terminating..."

Dez 17 13:00:33 iron systemd[1]: Starting Container foo...
Dez 17 13:00:33 iron systemd-nspawn[12750]: mount(/d/vm/foo/sys/fs/selinux) failed, ignoring: No such file or directory
Dez 17 13:00:33 iron systemd-nspawn[12750]: mount(/d/vm/foo/sys/fs/selinux) failed, ignoring: Invalid argument
Dez 17 13:00:33 iron systemd-nspawn[12750]: /etc/localtime is not a symlink, not updating container timezone.
Dez 17 13:00:33 iron systemd-nspawn[12750]: Failed to create /var/log/journal/15bfd317d6044649beb2e509acfd0cac: File exists
Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Main process exited, code=exited, status=1/FAILURE
Dez 17 13:00:33 iron systemd[1]: Failed to start Container foo.
Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Unit entered failed state.
Dez 17 13:00:33 iron systemd[1]: systemd-nspawn@foo.service: Failed with result 'exit-code'.
root@iron:~# ls -l /var/log/journal/15bfd317d6044649beb2e509acfd0cac
total 8192
-rw-r-----+ 1 root netdev 8388608 Jan 18  2015 system.journal
root@iron:~# rm -r /var/log/journal/15bfd317d6044649beb2e509acfd0cac
root@iron:~# systemctl start systemd-nspawn@foo
[ everything works ]
root@iron:~# 
@poettering poettering added bug 🐛 Programming errors, that need preferential fixing nspawn labels Dec 23, 2015
@poettering poettering added this to the v229 milestone Dec 23, 2015
@poettering
Copy link
Member

Fix waiting in #2466

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Programming errors, that need preferential fixing nspawn
Development

No branches or pull requests

2 participants