Quoting Matthias P. Wuerfl ([email protected]): > Hi. > > I Updated my Lucid-Container and it stopped working because of > udev/mounting issues. After following some do-this-do-that-advices it > works right now but i don't fully understand why. > > What is the difference between: > > - the fstab-file mentioned in the containers configfile > - /etc/fstab > - /lib/init/fstab? > > Which of the therein mentioned filesystems get mounted in which order? > Which program does it? I was told to deactivate "mountall" in /etc/init, > but filesystems get mounted. Why?
the containers fstab config file gets read first by lxc to set up basic mounts. Next, upstart's mountall consults /lib/init/fstab. That's the one which will usually prevent container startup from proceeding. The lxcguest package for ubuntu will force upstart to mount an empty version of that file before mountall runs. So if you install lxcguest then mountall can safely run, which makes your container safer against package updates. Then finally mountall will consult /etc/fstab. -serge ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Lxc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxc-users
