-
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
Cannot open self /usr/bin/docker-compose or archive /usr/bin/docker-compose.pkg #1135
Comments
👍 I'm experiencing this too... not sure what extra info would be useful to help debug |
how have you installed it? what operating system are you using? what's the output of |
I've installed via the curl + chmod technique and I'm on ubuntu 14.10 (utopic). And output as requested...
|
I've installed
|
does it work when you install compose with pip? |
I had same problem, it was because of permissions. This helped: |
@funkyfuture I installed with |
@funkyfuture I've been running the pip version of the install since your suggestion and it has been stable since. This seems specific to the curl method. I haven't tried the altered permissions that @hajaalin suggested so can't give feedback on that. |
Same problem here
|
I have the same problem as well. I'm on Mac OSX. |
Docker-compose requires not only |
Agree with @frol and @hajaalin -- adding read permission fixed the issue for me. Perhaps the documentation should be updated (https://docs.docker.com/compose/install/#install-compose) and this issue closed. |
I still have the issue, inspite of giving the read permission : This doesn't solve the issue on OEL-6.5 (& higher) OS. |
I'm experiencing the same issue on Centos 6.5...In my case the issue is worse because it doesn't consistently happens...meaning I usually can run |
+1 for this issue. I found the binary file has been changed(version 1.3.1) # ls -l /usr/bin/docker-compose
-rwxr-xr-x 1 root root 151325 Jun 26 09:37 /usr/bin/docker-compose The correct file is:
|
I'm experiencing the same issue on Ubuntu 14.04.
I fixed this by downloading file from browser. |
Same problem here. I need to reinstall docker-compose every time I reboot my server.
docker version
docker info
|
Nothing in the |
This is pretty weird. It seems that some process should be changing the permissions. What I end up doing was to set the immutable bit using chattr so I did: remember removing the bit using |
Anyone experiencing this issue, please tell us:
|
Hi @aanand, yesterday I tried to reboot my server but the problem didn't occur. Today it happened again:
We use Centos6. It could be the problem? |
@wrenzi Your
Looks like you downloaded it to Can you check the value of your |
@aanand, you are right. I changed it because the /usr/local/bin/ was not in my $PATH (now it is) I removed the installation and I installed it again in the default path:
If the problem occurs again I'll write here. Thank you very much. |
To anyone else experiencing the issue:
This might be an issue with improperly configured |
|
|
|
OK, then something on your system is changing the file. Nothing in Compose or the set of Docker tools would do that. Perhaps something that runs when you start a shell, or when you log in. |
I've been doing some digging and have a theory. A quick test... touch /tmp/test.sh
vi /tmp/test.sh
#!/bin/bash
echo foo
chmod +x /tmp/test.sh
sh /tmp/test.sh Looks like the way PyInstaller handles one-file executables is that it expands them in to The workaround is to install using |
…alid ELF file to stop prelinking breaking compose Signed-off-by: Garth Bushell <garth@garthy.com>
we had the issue today on a travis ci vm we use for a private repo |
This is still broken on Ubuntu 16.04.
Installing with Maybe you should drop the curl installation and require pip. Alternatively, advise to use pip as the preferred method and move curl to the alternative installation methods, with a link to this issue. Both solutions are going to save time to many people. Just in case it would need a writable /usr/local/bin similarly to what you suggest to do to make the download easier, that's against any security guideline. I didn't even attempt it. |
On Ubuntu 14.04, any installer that strips the binary will break it. It will truncate it to a 29680 byte file and will result in the error message shown in the subject. |
same problem #docker-compose yeah, i have solved this problem now! you can do like this.do not use the command line choose the way of downloading the file , that's OK. now you can use docker-compose --version to test whether your docker-compose is installed |
Same problem, but works by pip. SO: Fedora 25 |
Same problem, reason is curl download was incomplete. And no error output!!! |
Ran into this while packaging
You can find a little more info on RPM stripping - and other ways to disable it - at http://livecipher.blogspot.com/2012/06/disable-binary-stripping-in-rpmbuild.html |
Same problem, I just download it from github, followed by @fae88 instructions, I had to run this command to solve permissions issue:
|
Same problem, but I just reinstall it, then it work fine. |
[1191] Cannot open self /usr/local/bin/docker-compose or archive /usr/local/bin/docker-compose.pkg I also encountered this problem,Use curl to get.Network instability leads to this problem. |
This problem was solved, I did nothing but download the "docker-compose-Linux-x86_64" file again. The network sucks! |
Stumbled into this problem too, and as @garthy reported it's because of prelink |
sudo curl -L "https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose It solves the problem for me. |
Thank you. It works. |
I fixed it. It is because my desk is full, so I deleted all of images and containers by: docker rm $(docker ps -aq)
docker rmi $(docker images -q) |
me too |
me too |
Same issue on Linux Mint. |
I ran this command as root user, and it worked for me. |
Dude thanks a lot! Works like a charm |
|
this solved the problem |
I installed
docker-compose
on my server I reconnect later it said :I have to reinstall it all the time :/
Thanks for your help!
The text was updated successfully, but these errors were encountered: