Exec /init permission denied when starting container

[mdeboer]

I upgraded porter using Docker and I now get the following exception:
starting container process caused "exec: \"/init\": permission denied"

Docker image used (SHA256): b276b17f9b65a98ede4cb609f8336ab16482e401a8938db3f5003124420089b7 which is tagged as opensuse/portus:2.5 and opensuse/portus:latest.

I see it hasn't been released either so why tag this with a version or even latest when this isn't stable?

Version 2.4.3 works fine.

[bretep]

I'm also getting this after upgrading

[invy]

The same for me. ./init script is lacking executable permission. (Updated to the version tagget 2.5)
Strangely enough, the Dockerfile contains the line:

Portus/docker/Dockerfile

Line 8 in a1b9f2e

RUN chmod +x /init && \

Or was the image built from other Dockerfile...

[stefankip]

Same here, reverted to head.

[invy]

Same here, reverted to head.

FYI: workaround would be to specify the command in your deploy/compose file to call a chmod +x /init first and then the init itself.

[stefankip]

Thanks, but for me it's much easier to just revert to head ;-)

[bretep]

Yeah, I ended up reverting as well. If the fix is that easy, why not fix it and release again?

[mdeboer]

Yeah, I ended up reverting as well. If the fix is that easy, why not fix it and release again?

Because it's unclear why it occurred as apparently the Dockerfile is fine:

The same for me. ./init script is lacking executable permission. (Updated to the version tagget 2.5)
Strangely enough, the Dockerfile contains the line:

Portus/docker/Dockerfile

Line 8 in a1b9f2e

RUN chmod +x /init && \

Or was the image built from other Dockerfile...

However I agree, this should be fixed asap by untagging 2.5 and reverting the latest tag to 2.4.3. I also see no mention anywhere of 2.5 so I think it was unintended to be released already.

[dkowis]

Still an actual problem. I guess the tag never got reverted?

[harmeetsinghghotra]

Here's how I fixed it:

• Create a Dockerfile with the following content:

FROM opensuse/portus:2.5
RUN chmod +x /init

• Built a new docker image with:

docker build . -t opensuse/portus:2.5.1

That's it!

[tienthanh2509]

I am workaround by change entrypoint from /init to /bin/sh /init temporary without rebuild

# docker-compose.yaml
services:
  portus:
    image: opensuse/portus:2.5
    env_file:
      - config/portus.env
    entrypoint:
      - /bin/sh
      - /init

[stale]

Thanks for all your contributions!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[kovetskiy]

still appears to be not solved

[jimmybrancaccio]

I can confirm this is still not resolved, however using workaround suggested here does get things going.

[Jean-Baptiste-Lasselle]

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 #2241 (comment)

:)

I will read any feedback from you with interest

[stale]

Thanks for all your contributions!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[Persi]

This is still an issue with Imagetag 2.5.

[pciavald]

this issue still exists...

[9-9-9-9]

Almost 2 years and still no one cares about fixing this

[tienthanh2509]

Suggest replacing Portus with Habor, since this project seems to be inactive.

https://landscape.cncf.io/card-mode?category=container-registry&grouping=category&selected=harbor

[mdeboer]

+1 for Harbor, works perfectly

[teksturi]

Still exits.