tianon / boot2docker-debian Goto Github PK

Hi,

I wanted to start afresh so I removed **everything* from everywhere and proceeded with installing Docker Toolbox.

Now I am getting the following: Could not read CA certificate "/Users/idanadar/.boot2docker/certs/boot2docker-vm/ca.pem": open /Users/idanadar/.boot2docker/certs/boot2docker-vm/ca.pem: no such file or directory

I understand the error, but I do not understand how to correct it.

As a matter of facts I don't know if this project is still even supported but I rly need some lightweight iso to run docker on VM. My problem with boot2docker/boot2docker is that they use tinylinux and while it has some superb advantages I simply can't make it work like I'd like to. I'd rly love to try this one out but unfortunately I'm not able build it.

While building Dockerfile.docker and running RUN apt-key adv --keyserver ha.pool.sks-keyservers.net --recv-keys 58118E89F3A912897C070ADBF76221572C52609D I just get server timeout - seems like the key can't be found.

I know this is still a bit early in development. However, it would be nice to get some idea of what this is going to require to run. One of the nice features of the original boot2docker is that it was so lightweight (e.g. minimal memory usage, all in memory OS, quick startup/shutdown time, barebones feature-wise). This made it useable even for sophisticated calculations on a laptop. What sort of specs will/are we looking at with this new version of boot2docker.

I have a container that I start like this

docker run --name frontend -p 8080:80 -v /path/to/html:/usr/share/nginx/html:ro -d nginx

In my html folder, I have a bower_components folder. Inside this, there is a folder my_code that is installed from GitHub. When I attach to the container and ´ls´ inside my_code it shows Killed. If I navigate to the bower_components and type my and try to tab into the my_code folder, the attach session is stopped / killed. I can even delete the my_code folder and create a new empty directory with the same name and it behaves the same. The difference between my_codeand the other folders in bower_components that works as expected is that my_code is installed from GitHub rather then the bower registry, like this:

   //bower.json:

   "my_code": "https://github.com/klokoy/my_code.git"

Hi,

sorry if this has been explained somewhere else, but i couldn't find any documentation on this...

running ubuntu 15.04:
While i am able to successfully run docker-machine create -d virtualbox --virtualbox-memory=2048 docker-vm, i can't seem to get a working vm running build by make boot2docker-virtualbox.iso.

If i copy the resulting iso to ~/.docker/machine/cache/boot2docker.iso the vm is started, but docker-machine is unable to ssh into it...

&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i /home/strowi/.docker/machine/machines/docker-vm/id_rsa -p 42957 docker@localhost exit 0] []  <nil> <nil> <nil> [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>}
SSH cmd err, output: exit status 255: 
Error getting ssh command 'exit 0' : exit status 255
Getting to WaitForSSH function...
Testing TCP connection to: localhost:42957
Using SSH client type: external
About to run SSH command:
exit 0
...

Since i can manually run ssh and get a password-prompt, i guess this is a problem with the ssh-keys?
Can anyone verify this or help me out?

Since xhyve can't directly boot an ISO (from anything I can find), I'm thinking that perhaps it would be useful for us to release a boot2docker-xhyve.tar.xz (possibly .tar.gz instead since Go has better support for .gz...) which contains the kernel, initrd, and a cmdline file with boot arguments.

However, it does seem a little bit strange to make xhyve an explicit variant when all that's different is going to be VARIANT_ID and VARIANT in os-release and the fact that it's not released as an ISO.

I'm also not certain if we need nasty sleep hacks in our formatting script like in boot2docker/boot2docker#981, given that we're using the full Debian-provided tools for partitioning.

Using a build of docker-machine from @ehazlett, I have been testing the ng-b2d. One issue I've come across is due to how the shared folders are mounting my home directory. The ownership of everything is showing as root:vboxsf which is causing shared volumes to not work as expected when I am running as a non-root user in my container. I am running VirtualBox 5.0.0r101573 on OS X 10.10.4.

I couldn't find the kernel configs anywhere inside the VM. Are they missing?