Improper permissions on Portus init script
It's currently impossible to run opensuse/portus:2.5 since the /init script used as the entrypoint lacks the execute bit.
~/Desktop $ docker run -it opensuse/portus:2.5
Unable to find image 'opensuse/portus:2.5' locally
2.5: Pulling from opensuse/portus
ab9e8de21875: Pull complete
760a221d5360: Pull complete
Digest: sha256:fd014f18cef904c5d85b37b7aca36c1d62a2f36e4b93d75c8cc039ea93b359bd
Status: Downloaded newer image for opensuse/portus:2.5
docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "exec: \"/init\": permission denied": unknown.
~/Desktop $ docker run -it --entrypoint= opensuse/portus:2.5 bash
cd447a2256f7:/ # ls -la
[snip]
-rw-r--r-- 1 root root 3089 May 6 11:42 init
cd447a2256f7:/ #
ping @mssola
any update ?
Hey @Ashtonian @flavio @akx I am scanning all portus issues to give this to all who have had problems with portus images
Successfully repaired opensuse/portus:2.5 OCI container image
Hi @mdeboer @bretep @invy @stefankip @dkowis This time it's done, I have a solution to use, all details https://github.com/SUSE/Portus/issues/2241#issuecomment-593370789
It solves many of the issues I've scanned on portus project, including this one, like garbage collection keep latest feature, proper sync, I also have a working clair scanner (I think you might be interested Ash , remembering from the comments of your docker-compose.yml :) )
:)
I will read any feedback from you all with interest
I think this is still an issue:
# docker run -it opensuse/portus
Unable to find image 'opensuse/portus:latest' locally
latest: Pulling from opensuse/portus
ab9e8de21875: Already exists
760a221d5360: Already exists
Digest: sha256:fd014f18cef904c5d85b37b7aca36c1d62a2f36e4b93d75c8cc039ea93b359bd
Status: Downloaded newer image for opensuse/portus:latest
docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/init": permission denied: unknown.
ERRO[0002] error waiting for container: context canceled
+1