[ 
https://issues.apache.org/jira/browse/TINKERPOP-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487796#comment-16487796
 ] 

ASF GitHub Bot commented on TINKERPOP-1897:
-------------------------------------------

Github user FlorianHockmann commented on the issue:

    https://github.com/apache/tinkerpop/pull/802
  
    No, you're right. That is something that is very unlikely to occur and I 
can't think of other (more likely) reasons where the build of the docker images 
could fail as they really only copy the packaged artefacts together with the 
`docker-entrypoint.sh` scripts into the image.
    It is more likely that the built images themselves stop working for some 
reason, but we couldn't find that during the maven build anyway. So making it a 
habit to check the Docker images before a release seems to be the better option 
to me.
    
    I'll push a commit to remove the `.docker` file option and add a note to 
the docs section you linked.


> Provide Docker images of Gremlin Server and Console
> ---------------------------------------------------
>
>                 Key: TINKERPOP-1897
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1897
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: console, server
>    Affects Versions: 3.2.7
>            Reporter: Florian Hockmann
>            Assignee: Florian Hockmann
>            Priority: Major
>
> TinkerPop should provide Docker images of Gremlin Server and Gremlin Console 
> that are deployed together with each release.
> This originated from the mailing list:
> [https://lists.apache.org/thread.html/744ae19afa9b2fd1984c1e11114dddc588e98786d9c21b633aab8bfa@%3Cdev.tinkerpop.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to