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
When using the CLI images, it is implied that you should set a CMD (and this is shown in the one CLI example via command line), but it would help if at least one docker compose example and/or Dockerfile example showed this explicitely - it could be a CLI example running phpunit, which would be a common use case.
I tried setting up an ENTRYPOINT instead of a CMD, which overwrote the ENTRYPOINT of the image and lead to unexpected results (like php.ini settings not being set up), so a warning not to use ENTRYPOINT in a Dockerfile might also help, as most docker tutorials advise on using ENTRYPOINT instead of CMD, or using both together for executable containers.
The text was updated successfully, but these errors were encountered:
moufmouf
added a commit
to moufmouf/docker-images-php
that referenced
this issue
Jun 20, 2019
When using the CLI images, it is implied that you should set a CMD (and this is shown in the one CLI example via command line), but it would help if at least one docker compose example and/or Dockerfile example showed this explicitely - it could be a CLI example running phpunit, which would be a common use case.
I tried setting up an ENTRYPOINT instead of a CMD, which overwrote the ENTRYPOINT of the image and lead to unexpected results (like php.ini settings not being set up), so a warning not to use ENTRYPOINT in a Dockerfile might also help, as most docker tutorials advise on using ENTRYPOINT instead of CMD, or using both together for executable containers.
The text was updated successfully, but these errors were encountered: