-
Notifications
You must be signed in to change notification settings - Fork 369
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
Tar problem deploying an app on Deis #64
Comments
The problem is only occurring with Docker using overlayfs as storage driver which is now the default for CoreOS. |
Any idea for a fix? |
Here's the answer I got from Meteor (cf meteor/meteor#5762):
My Dockerfile is now looking something like that :
You just have to launch the |
Okay. That's exactly as this I think: https://github.com/meteorhacks/meteord#2-running-a-meteor-bundle-with-docker |
Hope we could close this. |
Don't have time to test if the meteord image is working properly on the current Docker 1.10.0-dev with OverlayFS as the storage driver ... It is perfectly working with using https://github.com/meteorhacks/meteord#2-running-a-meteor-bundle-with-docker on an OverlayFS-based Docker Engine so ... let's close this issue ;) |
I do not encounter this error on non OverlayFS-based Docker engine, do you ?
|
Just to add, I am also seeing such errors occasionally for my Meteor apps automatic builds on Docker hub. But sometimes it works. I just have to rerun a build. |
BTW, I wrote about this to Docker and they said that they fixed it on Docker Hub. So this |
I tried to deploy a meteor app on a Deis cluster : http://deis.io (which simply takes the Dockerfile and produces an image before running it) but it failed due to tar errors while installing Meteor:
The error
Directory renamed before its status could be extracted
seems to be linked to a permission fault but I didn't found any way to fix this. Onbuild or devbuild don't change anythingPS: The error is not occurring while building the image locally with either onbuild or devbuild.
Thank you in advance for your support
The text was updated successfully, but these errors were encountered: