-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local directories periodically fail to be mounted. #443
Comments
Could you reduce your |
Put the minimal recreate into https://github.com/dancrumb/github-fig-443 |
The system that I am seeing this on:
My local system, that I have not been able to recreate this on:
|
Let me know if you want me to run any instrumented versions of fig to get more information here. |
Were you able to recreate this issue locally? |
+1 |
Unfortunately, we're going to have to abandon fig because of this instability. Switching to crane. I'm happy so provide more data, if you need it, but it'll take me longer, since I won't have fig running any more. |
+1 |
I switched to crane and ended up hitting the same issue and was eventually able to replicate it via Docker directly. See my comments here #328 (comment) Upgrading to the latest Docker dev version fixed the issue for me. Build instructions here, https://docs.docker.com/contributing/devenvironment/ |
Docker 1.3 was just released today, so you probably don't even have to build it yourself |
Oh, brilliant :) |
@rolo Let me know if Docker 1.3 fixes it and I can close this! |
@bfirsh Yep, have just tested with Docker 1.3 and all seems fine. Cheers! |
Woot! |
I'm using Docker 1.3 and first time I ran fig everything's fine. But when I have restarted boot2docker I met the same problem. |
I am having this problem on osx. Docker 1.3.1, fig 1.0.1, boot2docker 1.3.1 |
I'm also getting this issue. Docker 1.3.0 boot2docker 1.3.0 and fig 1.0.1. Running OS X Yosemite. |
I have the same issue with Docker 1.4.1 boot2docker v1.4.1 and fig 1.0.1. Running OSX 10.9.5. |
Docker 1.4.1 on Ubuntu 14.04; I believe I'm still seeing this. |
+1 still happening here, please re-open the issue. $ docker version $ fig --version Update: after reverting back to Docker 1.3.1 and it works fine |
looks like it's being addressed on #622 |
I'm also having the same issue. Here's my configuration: $ docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.4
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.0
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 4595d4f
$ fig --version
fig 1.0.1
$ cat fig.yml
webdev:
build: ./docker/apache-dev
command: "/usr/sbin/apache2ctl -D FOREGROUND"
ports:
- "80:80"
volumes:
- "./apache-logs:/var/log/apache2"
- "./:/var/www"
working_dir: /var/www
links:
- dbdev
dbdev:
build: ./docker/mysql
ports:
- "3306:3306"
volumes:
- ./app/database:/var/lib/mysql and current dir is not mounted in /var/www $ fig run webdev ls -l /var/www
total 0
$ ls -l
total 30236
.... Here's webdev inspect result: [{
"AppArmorProfile": "",
"Args": [
"-D",
"FOREGROUND"
],
"Config": {
"AttachStderr": true,
"AttachStdin": false,
"AttachStdout": true,
"Cmd": [
"/usr/sbin/apache2ctl",
"-D",
"FOREGROUND"
],
"CpuShares": 0,
"Cpuset": "",
"Domainname": "",
"Entrypoint": [],
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"APACHE_RUN_USER=www-data",
"APACHE_RUN_GROUP=www-data",
"APACHE_LOG_DIR=/var/log/apache2",
"SERVER_NAME=localhost",
"APACHE_LOG_LEVEL=info",
"REFRESHED_AT=2014-11-12"
],
"ExposedPorts": {
"80/tcp": {}
},
"Hostname": "5191f6ad9b09",
"Image": "my_project_webdev",
"MacAddress": "",
"Memory": 0,
"MemorySwap": 0,
"NetworkDisabled": false,
"OnBuild": null,
"OpenStdin": false,
"PortSpecs": null,
"StdinOnce": false,
"Tty": false,
"User": "",
"Volumes": {
"/var/log/apache2": {},
"/var/www": {}
},
"WorkingDir": "/var/www"
},
"Created": "2014-12-19T13:35:41.445992488Z",
"Driver": "devicemapper",
"ExecDriver": "native-0.2",
"HostConfig": {
"Binds": [
"/home/gildas/projects/my_project/apache-logs:/var/log/apache2:rw",
"/home/gildas/projects/my_project:/var/www:rw"
],
"CapAdd": null,
"CapDrop": null,
"ContainerIDFile": "",
"Devices": null,
"Dns": null,
"DnsSearch": null,
"ExtraHosts": null,
"IpcMode": "",
"Links": [
"/my_project_dbdev_1:/my_project_webdev_1/my_project_dbdev_1",
"/my_project_dbdev_1:/my_project_webdev_1/dbdev",
"/my_project_dbdev_1:/my_project_webdev_1/dbdev_1"
],
"LxcConf": null,
"NetworkMode": "bridge",
"PortBindings": {
"80/tcp": [
{
"HostIp": "",
"HostPort": "80"
}
]
},
"Privileged": false,
"PublishAllPorts": false,
"RestartPolicy": {
"MaximumRetryCount": 0,
"Name": ""
},
"SecurityOpt": null,
"VolumesFrom": [
"c0574d4f51ca1d0705ce7248281f1c3c26a3c5da57c1acecc821f2a0e21be5a8"
]
},
"HostnamePath": "/var/lib/docker/containers/5191f6ad9b09f32d1e7fdc9cba191970175ec49096aa1d354c5b7121af174ac0/hostname",
"HostsPath": "/var/lib/docker/containers/5191f6ad9b09f32d1e7fdc9cba191970175ec49096aa1d354c5b7121af174ac0/hosts",
"Id": "5191f6ad9b09f32d1e7fdc9cba191970175ec49096aa1d354c5b7121af174ac0",
"Image": "7d06a618867fa2c70578909a948314f3075a5febb78fcf43cd459c9c60199d57",
"MountLabel": "",
"Name": "/my_project_webdev_1",
"NetworkSettings": {
"Bridge": "docker0",
"Gateway": "172.17.42.1",
"IPAddress": "172.17.0.60",
"IPPrefixLen": 16,
"MacAddress": "02:42:ac:11:00:3c",
"PortMapping": null,
"Ports": {
"80/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "80"
}
]
}
},
"Path": "/usr/sbin/apache2ctl",
"ProcessLabel": "",
"ResolvConfPath": "/var/lib/docker/containers/5191f6ad9b09f32d1e7fdc9cba191970175ec49096aa1d354c5b7121af174ac0/resolv.conf",
"State": {
"Error": "",
"ExitCode": 0,
"FinishedAt": "0001-01-01T00:00:00Z",
"OOMKilled": false,
"Paused": false,
"Pid": 26303,
"Restarting": false,
"Running": true,
"StartedAt": "2014-12-19T13:35:42.112575725Z"
},
"Volumes": {
"/var/log/apache2": "/var/lib/docker/vfs/dir/8d8ace23570f715d1b25b68b5bed9503abbd5e22fbb1707757f7972d7f61050b",
"/var/www": "/var/lib/docker/vfs/dir/17436c6b2c98d10bd253d66453844904de5051c0514e48078c001ff6ce90007d"
},
"VolumesRW": {
"/var/log/apache2": true,
"/var/www": true
}
}
] |
@gquemener You've only updated your client to 1.4.1, you need server 1.4.1 |
Oh gosh, I totally missed that! Thanks @cpuguy83 :D |
shim executor: clean state dir if newProcess() failed
I'm seeing an issue whereby a local directory that I mount to a container is, intermittently, not actually mounted.
Dockerfile
loadsnapshot.sh
fig.yml
The goal here (which may be obvious) is to start up a data container (pdsvol) and then populate it with some data that's running on my machine. pdsvol is then shared by a bunch of other containers.
The way I run this is to call
and then
What I expect to see is
and, sometimes I do. However, sometimes I see:
After a lot of debug effort, I was able to run my command without the
--rm
and then inspect the remaining containers.When I diffed the results I saw::
Successful
Failed
So, it appears that the wrong volume is being mounted at
/snapshot
I see this very regularly. If I run my command 10 times, I'll see it a couple of times.
If I run the docker equivalent, I never see this issue.
The text was updated successfully, but these errors were encountered: