An entrypoint or command defined in the image are ignored

[spaulg]

Description

If the compose file does not declare an entrypoint or command, but the image does, the container is started without a command.

This is because the service entrypoint is overridden but the image entrypoint/command is not accessible to solo.

Acceptance Criteria

1. Given an image that defines an entrypoint and/or command
   When an entrypoint and comand are not defined in the project file
   Then the entrypoint and command in the image are used instead

[spaulg]

Workaround is to specify an entrypoint or command. To handle this, I think an additional step to run compose build and inspect the built image to extract details of the entrypoint/command would be required.

If the image has already been built, is there a way to know this? At what point does compose decide to rebuild an image if the associated files have been updated?