SvenDowideit
commented
9 years ago @tianon this may be a good reason to merge https://github.com/boot2docker/boot2docker/pull/692 for 1.5.0
the 3.16.x series seem to be very EOL
Open lunaticare opened 9 years ago
SvenDowideit
commented
9 years ago @tianon this may be a good reason to merge https://github.com/boot2docker/boot2docker/pull/692 for 1.5.0
the 3.16.x series seem to be very EOL
foxx
commented
9 years ago I had this problem today as well
SvenDowideit
commented
9 years ago @foxx - on boot2docker 1.4, 1.5 or 1.6?
foxx
commented
9 years ago Ah wait, sorry no I commented on the wrong issue, my bad
klokoy
commented
9 years ago Any news on this?
I have have this problem both due to npm link on server code and bower link on client code. Both creates symlinks.
gabriel403
commented
9 years ago Any news on this? Getting a very similar issue but can't track it down (don't think I have any symlink either)
root@f4f4da520c44:/# ll /usr/share/nginx/html/vendor/slimphp-api/slim-oauth/
Killed
root@f4f4da520c44:/#
andrewgdavis
commented
8 years ago Here are the steps that caused this issue for me, and a potential work around. (I can't explain the behavior, or how to approach debugging it.)
note: im still using 1.8.3 due to some kernel issue in docker v1.9.1
mkdir ./mount
cd mount
ln -sf ~/my-git-repo ./myproject
docker -D run -it --rm -v `pwd`/mount:/home/foo/mount centos:7 bash
cd /home/foo/mount
ls -la
lrwxr-xr-x 1 1000 1000 34 Jan 8 19:10 myproject -> /Users/dir/my-git-repo/does/not/have/link/propagated/through/vmok, i get it. can't propagate the symlink.
so exit the container and i remove the link
rm ./myprojectnow i try it with a full clone and name the directory "myproject" instead of the link, with the same name as the link that was removed
cd mount
git clone https://github.foo.bar.com/mine/my-git-repo myproject
docker -D run -it --rm -v `pwd`/mount:/home/foo/mount centos:7 bash
cd /home/foo/mount
ls -la
cd myproject
DEBU[0016] [hijack] End of stdout
DEBU[0016] End of CmdRun(), Waiting for hijack to finish.
# above command exits container
echo $?
137That was unexpected-- I am not able to enter into the mounted directory that is no longer a symlink. I thought it would have been a "clean" restart.
Potential workaround: If i do the same steps as above and change "myproject" to "foo-project" I am able to "cd foo-project" and enter into the mounted directory. this works (i think because i did not try to setup a symlink to it)
git clone https://github.foo.bar.com/mine/my-git-repo foo-projectEnv Info: Darwin xxx 14.3.0 Darwin Kernel Version 14.3.0 docker-machine version 0.4.1 (e2c88d6) Docker version 1.8.3, build f4bf5c7 Storage Driver: aufs Kernel Version: 4.1.10-boot2docker CPUs: 5
MatthiasEgli
commented
8 years ago I experienced the same error as described by @andrewgdavis. My workaround was to restart docker-machine, afterwards I could access to folder without problems. It is likely related to the way the virtual machine is transparently allowing access to the mac file system.
Hi everyone,
first reported the issue here https://github.com/docker/docker/issues/10118 but it appears to be related to boot2docker.
I launch container (Ubuntu 14.10)
docker run -ti -v /Users/lunaticare/Documents/dev:/double ubuntu:latest bashand try to see the contents of subdirectory:# ls /double/doubleThen I get only message "Killed". I suspect this may be due there were symlinks to the subdirectory. It is unlikely to be connected to the contents of the directory - I created a directory with a different name, moved contents to it, files were listed OK. Other dirs in the volume have the same access permissions and are shown correctly.docker versiondocker inspect:docker info:uname -admesg: