Error after building image: /bin/bash: /usr/local/bin/repo2docker-entrypoint: Permission denied
See original GitHub issueBug description
running repo2docker on an empty directory (to get a default python environment), I get:
jupyter-repo2docker .
Picked Local content provider.
Using local repo ..
Using RBuildPack builder
...
Step 44/46 : COPY /repo2docker-entrypoint /usr/local/bin/repo2docker-entrypoint
---> Using cache
---> 1a386e8b05e3
Step 45/46 : ENTRYPOINT ["/usr/local/bin/repo2docker-entrypoint"]
---> Using cache
---> dea2b546b748
Step 46/46 : CMD ["jupyter", "notebook", "--ip", "0.0.0.0"]
---> Using cache
---> 71d561c90128
{"aux": {"ID": "sha256:71d561c901289655ff31f29b3209774cae2c3853ea67e132c05a1215a47db035"}}Successfully built 71d561c90128
Successfully tagged r2d-2e1567611552:latest
/bin/bash: /usr/local/bin/repo2docker-entrypoint: Permission denied
Expected behaviour
I thought the jupyter notebook would launch.
Actual behaviour
Error
How to reproduce
Your personal set up
-
OS: manjaro linux
-
Docker version:
docker version
Client: Version: 19.03.1-ce API version: 1.40 Go version: go1.12.7 Git commit: 74b1e89e8a Built: Sat Jul 27 21:08:50 2019 OS/Arch: linux/amd64 Experimental: false
Server: Engine: Version: 19.03.1-ce API version: 1.40 (minimum version 1.12) Go version: go1.12.7 Git commit: 74b1e89e8a Built: Sat Jul 27 21:08:28 2019 OS/Arch: linux/amd64 Experimental: false containerd: Version: v1.2.7.m GitCommit: 85f6aa58b8a3170aec9824568f7a31832878b603.m runc: Version: 1.0.0-rc8 GitCommit: 425e105d5a03fabd737a126ad93d62a9eeede87f docker-init: Version: 0.18.0 GitCommit: fec3683
- repo2docker version
repo2docker --version
0.10.0
The only thing I did differently was to install as --user rather than root:
python3 -m pip install --user jupyter-repo2docker
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top GitHub Comments
Had the same problem, file permissions on the extra point were set weirdly for whatever reason.
Here’s a patch that makes it work for me:
These were file permissions in the built docker image for me, which caused the issue:
I have the same issue and it is reproducible if you install it repo2docker in Travis with a simple pip install. Because I do not see any PR I will make one