Daniel, Thanks for your answer. I appreciate it for sure and I know all the hassle you have to deal with being a debian package maintainer. Still my experience with lxc so far has been a big pain compared with vserver.
Le 29/07/2012 21:52, Daniel Baumann a écrit : > On 07/29/2012 09:33 PM, Loïc wrote: >> Damn, that's really not that polished: > we don't use the lxc-debian template in debian as lxc-debian, but > lxc-debconf, which is different, you might want to report such issues to > debian, not lxc upstream. That sounds like chinese to me. Sorry about that, but since you stated yourself that the debian wiki page is outdated and cannot be trusted, and since the documentation in /usr/share/doc/lxc is not providing any info close to the wiki page, where should I dig? >> 1/ "you must be root to change the hostname" message. > cosmetical, we drop some capabilities. That's ok, not my main problem so far. >> 2/ mount reports a lot of permission denied. > cosmetical, we drop some capabilities. That's ok, not my main problem so far. >> 3/ hwclock is unable to set the system clock > cosmetical, we drop some capabilities. That's ok, not my main problem so far. >> 4/ the sshd service which seems to have been installed from the template is >> unable to load its keys. > see the bug about missing preseeding in the debian bts. That's ok, not my main problem so far. >> All of which I am ready to deal with later, but the most important one for >> me is the messages I got after the boot process: > see the bug about missing preseeding in the debian bts. Would you be kind to point me to this bug number, since you probably know it? >> Which means that I'm stuck in the container console without a shell :( > see the bug about missing preseeding in the debian bts. Repeat: Would you be kind to point me to this bug number, since you probably know it? Addon: I care less about the bugs than with an up-to-date useful documentation, even if it implies that I have to manually work around any bug. But I would appreciate to know what I have to do. :) >> Following the advises here, I kindly installed the linux-container package, >> and installed the resulting .deb package from /var/cache/apt/archives into >> /usr/share/lxc. >> That seems to make no difference when I destroy and recreate my container. > because you need live-debconfig, not linux-container. There is a "linux-container" debian package, but no "live-debconfig" one. What am I supposed to do then, when no up to date documentation is available? >> I cannot believe that lxc is that immature. I may surely be missing a lot of >> things, or is the Debian packaging of lxc such a pity? > you are using debian testing, it's not called testing without purpose. > if you're not prepared to deal with temporary glitches, use debian stable. I agree with that. But it's not called "unstable" either, and it just started to freeze. So far, to me, without any up to date doc, this package is unusable. Should I believe that lxc was unusable for 18 months or that it's just a late bug? I know that you are the maintainer, and I appreciate your devotion. Thanks for replying. But keep in mind that without any usuable documentation, your efforts are worthless for the end users. So feel free to point me to a doc. If no doc. exists, I'll be happy to document that package with your help before wheezy goes to the stable state. Because, sorry to say that, comparing to vserver, my experience with lxc so far is terrible. -- Loïc ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
