Error `The "-c" option does not exist.` when running latest(1.4.1) docker image

[cpxPratik]

With the change of entry point to "/src/expose", the image now runs with command "/src/expose /bin/sh -c 'sed -i ....

But for some reason with this change, -c option is assumed to be from expose instead of sh. The container keeps restarting.

Contaienr log shows

Error `The "-c" option does not exist.

Previously on 1.3.4 version, it would run as "docker-php-entrypoint /bin/sh -c 'sed -i ...

[MeestorX]

Same problem for me.

[PKeidel]

+1 Same error here

[matthieumota]

This is a conflict between ENTRYPOINT and CMD. Docker run /src/expose /bin/sh -c serve this way, which is not at all correct and makes the CMD part unusable. Also, it's necessary to create a custom sh script as entrypoint to run /src/expose. I've made a PR #174

[clarg18]

That PR does not resolve the issue for me when using docker compose.

For now, I have changed the docker-compose.yml from

    image: beyondcodegmbh/expose-server:latest

to

    image: beyondcodegmbh/expose-server:1.3.4

[matthieumota]

PR is not merged so with latest image, you don't get that fix. You need to clone PR and build manually if you want to try.

[dbpolito]

While the PR is not merged and you want to run on latest image, change your docker-compose.yml to:

    image: beyondcodegmbh/expose-server:1.5.0 # or latest
    entrypoint: ["sh", "-c"]
    command: sed -i "s|username|${username}|g" ${exposeConfigPath} && sed -i "s|password|${password}|g" ${exposeConfigPath} && php expose serve ${domain} --port ${port} --validateAuthTokens

[TiiFuchs]

The problem still persists... :(

[matthieumota]

@TiiFuchs You can use my PR branch to fix problem. Wait to @mpociot to merge 🙏

[RogerSik]

Any news regarding this? We have also this issue.

[matthieumota]

@mpociot has merged #174 so if you also have issue, you need to update your package to Expose 2.

[RogerSik]

@matthieumota we are using the docker-compose with the image: expose-server:2.0.2

With the tag 1.4.0 we dont have this issue and with beginning this 1.4.1. This occour. Do we need to more then only update the image tag?

[matthieumota]

@RogerSik Be sure docker images is updated on your system. If we check on Docker Hub, image is properly build from last release

[RogerSik]

@matthieumota yes it is. It seems to have something todo with the database. After a new setup with a new database the error message doesn't appear more.

[sschlein]

Closing this issue because it's old. Please feel free to open a new one if it's still relevant.