Skip to content
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

Cannot access symlinks during build #5686

Closed
florentdestremau opened this issue Feb 18, 2018 · 7 comments
Closed

Cannot access symlinks during build #5686

florentdestremau opened this issue Feb 18, 2018 · 7 comments

Comments

@florentdestremau
Copy link

I just setup a jenkins server and I noticed that my builds failed because my docker-compose setup did not boot at all ! Here is the command that blocks everything.

jenkins@windoo-jenkins:~/workspace/Windoo Saas$ docker-compose -f docker-compose.test.yml up -d
Building php_test
Traceback (most recent call last):
  File "bin/docker-compose", line 6, in <module>
  File "compose/cli/main.py", line 71, in main
  File "compose/cli/main.py", line 124, in perform_command
  File "compose/cli/main.py", line 1001, in up
  File "compose/cli/main.py", line 997, in up
  File "compose/project.py", line 463, in up
  File "compose/service.py", line 326, in ensure_image_exists
  File "compose/service.py", line 989, in build
  File "site-packages/docker/api/build.py", line 150, in build
  File "site-packages/docker/utils/build.py", line 14, in tar
  File "site-packages/docker/utils/utils.py", line 103, in create_archive
IOError: Can not access file in context: /var/lib/jenkins/workspace/Windoo Saas/vendor/salavert/time-ago-in-words/bin/phpunit
Failed to execute script docker-compose

jenkins@windoo-jenkins:~/workspace/Windoo Saas$ ls -la vendor/salavert/time-ago-in-words/bin/phpunit 
lrwxrwxrwx 1 jenkins jenkins 33 Feb 18 16:22 vendor/salavert/time-ago-in-words/bin/phpunit -> ../vendor/phpunit/phpunit/phpunit

jenkins@windoo-jenkins:~/workspace/Windoo Saas$ ls -la vendor/phpunit/phpunit/phpunit
-rwxr-xr-x 1 jenkins jenkins 1277 Dec 10 08:06 vendor/phpunit/phpunit/phpunit

My docker-compose version:

docker-compose version 1.19.0, build 9e633ef
docker-py version: 2.7.0
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.1t  3 May 2016

On my pc it works like a charm with this configuration:

docker-compose version 1.18.0, build 8dd22a9
docker-py version: 2.6.1
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.1t  3 May 2016

It may have link with docker/docker-py#1841 ? But this issue is closed so I don't know..

@shin-
Copy link

shin- commented Feb 20, 2018

It'll be fixed in the next Compose release.

@florentdestremau
Copy link
Author

Great news ! 😃

For those interested in a immediate fix, just install back the 1.18.0 version (replace the version in the installer script):

sudo curl -L https://github.com/docker/compose/releases/download/1.18.0/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose

@shin- shin- added this to the 1.20.0 milestone Feb 20, 2018
@shin-
Copy link

shin- commented Feb 20, 2018

I'll close this as it was already fixed in master by #5631 . Thank you for your patience!

@simondiep
Copy link

I'm still running into this issue on 1.20.1

@florentdestremau's suggestion to rollback to 1.18.0 worked for me.

@bormisov1
Copy link

@simondiep +1, just updated to latest today

@shin-
Copy link

shin- commented Mar 30, 2018

Please make a proper bug report with the required info.

@gottook4blame
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants
@shin- @florentdestremau @simondiep @bormisov1 @gottook4blame and others