You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Container is not starting correctly after recreating via cosmos. The issue is the entrypoint-translation. On Creation, the entrypoint gets extracted from the dockerfile and added to the cosmos-compose wrongly.
What should have happened?
It should start container
How to reproduce the bug?
Use the following cosmos-compose, it fails to start the container.
It's not exclusive to this template, there are others which do not start as well.
The Issue seems to be how cosmos translates the entrypoint (The default one inside the dockerfile)
Also only seems to be happening when /bin/sh -c is used.
What happened?
Container is not starting correctly after recreating via cosmos. The issue is the entrypoint-translation. On Creation, the entrypoint gets extracted from the dockerfile and added to the cosmos-compose wrongly.
What should have happened?
It should start container
How to reproduce the bug?
Use the following cosmos-compose, it fails to start the container.
It's not exclusive to this template, there are others which do not start as well.
I'm using this image for mailu
Other details
The Issue seems to be how cosmos translates the entrypoint (The default one inside the dockerfile)
Also only seems to be happening when
/bin/sh -c
is used.Example which doesn't work:
Dockerfile:
Cosmos Compose:
System details
The text was updated successfully, but these errors were encountered: