Tag Info

New answers tagged

1

Dave C. above is correct about the problem being ssh not running. As I said in a comment, there was not anything in any log file that showed a problem. Stopping/Starting ssh did not have any effect, nor showed any errors anywhere. I just needed to drop the container and build a new one.


0

This has been fixed in releases of lxc >= 1.1 with the introduction of the fuse-filesystem lxcfs. Simply install and set up lxc with lxcfs.


0

Install schroot on your Fedora system. Schroot is a wrapper around chroot that allows non-root users to use predefined chroots and arranges for home directories, /proc, etc. to be present in the chroot. I wrote a schroot guide in How do I run 32-bit programs on a 64-bit Debian/Ubuntu? With a Fedora host system, the setup is mostly the same — it's mostly the ...


0

I bumped into similar issue a while ago in lxc with Ubuntu 14.04 as guest OS. I did some digging and it turned out that the limit nofile ... directive in mongodb upstart job somehow caused dpkg --configure call on mongodb-server package to exit with failure during mongodb post-installation process. Commenting the line allows the installation process to ...


0

chroot will not solve your problem at all. In fact, chroot will make you run this program as if you were in Ubuntu itself and not in Fedora. You will need a complicated setup to make them access your file system outside chroot. chroot is meant more for isolation. One good solution for your problem however is just to use environment variables. Maybe a small ...


0

/var/run/docker.sock is a socket so you need to use -S when testing for existence: FILE=/var/run/docker.sock while [ ! -S $FILE ] ; do inotifywait -t 2 -e create $(dirname $FILE) done


1

change your network hwaddr (on config container file) set ip of your bridge and make it up its same with http://febru.soluvas.com/2015/03/solved-failed-to-attach-bridge-virbr0.html



Top 50 recent answers are included