For me this seems not fixed.
ii apparmor 2.7.102-0ubuntu3 User-space
parser utility for AppArmor
ii lxc 0.7.5-3ubuntu56 Linux
containers userspace tools
root@kira:~# lxc-start -n jake
lxc-start: failed to mount rootfs
lx
After the workaround, my container is running.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/947617
Title:
After update, lxc does not start
To manage notifications about this bug go t
Serge,
This container I created with oneiric with the lxc-sshd template. It worked
there reasonably well (only needed to add a default route, which is missing).
I've compared (visually) what oneiric created for mounting and what precise
would have created. It seems there is only 1 difference. One
Me too.
As a really ugly workaround I thought about this...
(1) disable samba to run as daemon (add 'exit' in /etc/default/samba)
(2) sudo chmod a+rw /var/run/samba/*.tdb /var/lib/samba/*.tdb
This totally ruins the samba security, I expect. That's why I disabled
samba to start as a daemon.
--
s
After the workaround I did, samba started and was usable from a w2k in qemu.
(I did start chmodding only one file and manually starting smbd and then it
complained about another one and then another one...)
I don't know what's incomplete about this bug and I can confirm that it
still exists with
Public bug reported:
Binary package hint: samba
I've got win2k in a qemu vm and I'm using '-smb' with my home directory. When I
try to reach that network drive, smbd crashes. The log is below. And w2k
reports that the network path was not found.
Smbd reports that it is dumping core in /var/log/
Please note that there's a simple 'chmod g+rw /var/run/samba/message.tbd' fixes
the access denied and thus prevents the whole stacktrace.
But I just thought that I should report it anyways.
--
3.2.3 and qemu: could not init smb messaging context
https://bugs.launchpad.net/bugs/278712
You receive
