[
https://issues.apache.org/jira/browse/TAJO-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392142#comment-14392142
]
Jaehwa Jung commented on TAJO-1423:
-----------------------------------
No problem. :)
I checked active PR list. But you're so right and it seems to maintain
endpoints. :-)
I found a guidance for contribution to the docker standard library.
Please see following site.
https://docs.docker.com/docker-hub/official_repos/
I think we better create Tajo repository to following site.
https://github.com/docker-library
For example, postgresql maintain its docker source codes within docker-library
as follows.
https://github.com/docker-library/postgres
> Support official docker images
> ------------------------------
>
> Key: TAJO-1423
> URL: https://issues.apache.org/jira/browse/TAJO-1423
> Project: Tajo
> Issue Type: Task
> Reporter: Dongjoon Hyun
> Assignee: Dongjoon Hyun
> Attachments: TAJO-1423.patch
>
>
> This issue will be discussed in Tajo mailing list. The following is my
> proposal for official Docker.
> First of all, the official Tajo docker will be here.
> https://registry.hub.docker.com/u/tajo/centos6/
> https://registry.hub.docker.com/u/tajo/ubuntu14.10/
> (Please refer https://registry.hub.docker.com/u/sktelecom/ubuntu14.10-hdw/ )
> To do that, we need to make a offical `tajo` account in dockerhub.com and set
> an automatic build by specifying Tajo Docker source folder location.
> Docker source folder might have a similar level with `dev-support` folder.
> The structure will look like the followings.
> {code}
> dockerfiles
> ├── centos6
> │ ├── Dockerfile
> │ ├── ...
> │ └── README.md
> └── ubuntu14.10
> ├── Dockerfile
> ├── ...
> └── README.md
> {code}
> After thatn, whenever Tajo Github is updated, Dockerhub will automatically
> rebuild the docker images.
> Note that Dockerfile usually use the binary distribution of Tajo, e.g. 0.10.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
