[jira] [Created] (JCLOUDS-997) Docker: entrypoint and cmd should be nullable in org.jclouds.docker.domain.Config

["Josef Cacek (JIRA)" <ji...@apache.org>]

Josef Cacek created JCLOUDS-997:
-----------------------------------

             Summary: Docker: entrypoint and cmd should be nullable in org.jclouds.docker.domain.Config
                 Key: JCLOUDS-997
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-997
             Project: jclouds
          Issue Type: Bug
          Components: jclouds-labs
    Affects Versions: 1.9.1
            Reporter: Josef Cacek


Both configuration options {{cmd}} and {{entrypoint}}  should be nullable (with {{null}} as the default in {{org.jclouds.docker.domain.Config}} class. 

An empty list is used as the default now. As a result, the *entrypoint defined in the image is not used*. 

If cmd is only used to configure the entrypoint parameters then starting the image fails. For instance - something like this could be in httpd Dockerfile:
{code}
ENTRYPOINT ["apachectl"]
CMD ["start", "-DFOREGROUND"]
{code}

Then the jClouds doesn't use the entrypoint and it only tries to run "start -DFOREGROUND". Which fails miserably - there is no "start" executable on $PATH.

The entrypoint should also be configurable through {{org.jclouds.docker.compute.options.DockerTemplateOptions}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)