[
https://issues.apache.org/jira/browse/IGNITE-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Gillé updated IGNITE-10853:
-----------------------------------
Description:
According to the documentation
(https://apacheignite.readme.io/docs/docker-deployment) the official Docker Hub
repository is https://hub.docker.com/r/apacheignite/ignite. But the source
repository (the GitHub repository where the Dockerfile is) points to
https://github.com/ntikhonov/ignite, which is not the official Apache Ignite
GitHub repository. See the attached image for this.
You do have a Dockerfile in your official repository, see
https://github.com/apache/ignite/tree/7989173b4d64a681fd08b7d7bcda2d26559941ae/docker/apache-ignite.
And apparently your build process pushes the Docker image to the Docker Hub, so
the image on the Docker Hub is actually *correct*.
*But* there are multiple problems with this:
1. When looking at the Dockerfile via the Docker Hub web interface
(https://hub.docker.com/r/apacheignite/ignite/dockerfile), it's the wrong
Dockerfile! See the attached image for this
2. People might be mislead into thinking that
https://github.com/ntikhonov/ignite is the official Ignite GitHub repository if
they overlook that it's a fork
3. https://github.com/ntikhonov/ignite master branch is 2445 commits behind the
official master. Currently it seems that the Docker Hub automatic building is
deactivated, but if it gets activated (for building Docker images on each
GitHub repo push) an old / wrong Docker image will be created on Docker Hub and
it will stay wrong until your CI service pushes the correct one
Related:
- The Docker image was created in IGNITE-1046
- The Docker image is supposed to be turned into an official Docker image in
IGNITE-7190, but the PR has been open for one year already and seems to be
abandoned
was:
According to the documentation
(https://apacheignite.readme.io/docs/docker-deployment) the official Docker Hub
repository is https://hub.docker.com/r/apacheignite/ignite. But the source
repository (the GitHub repository where the Dockerfile is) points to
https://github.com/ntikhonov/ignite, which is not the official Apache Ignite
GitHub repository. See the attached image for this.
You do have a Dockerfile in your official repository, see
https://github.com/apache/ignite/tree/7989173b4d64a681fd08b7d7bcda2d26559941ae/docker/apache-ignite.
And apparently your build process pushes the Docker image to the Docker Hub, so
the image on the Docker Hub is actually *correct*.
*But* there are multiple problems with this:
1. When looking at the Dockerfile via the Docker Hub web interface
(https://hub.docker.com/r/apacheignite/ignite/dockerfile), it's the wrong
Dockerfile! See the attached image for this
2. People might be mislead into thinking that
https://github.com/ntikhonov/ignite is the official Ignite GitHub repository if
they oversee that it's a fork
3. https://github.com/ntikhonov/ignite master branch is 2445 commits behind the
official master. Currently it seems that the Docker Hub automatic building is
deactivated, but if it gets activated (for building Docker images on each
GitHub repo push) an old / wrong Docker image will be created on Docker Hub and
it will stay wrong until your CI service pushes the correct one
Related:
- The Docker image was created in IGNITE-1046
- The Docker image is supposed to be turned into an official Docker image in
IGNITE-7190, but the PR has been open for one year already and seems to be
abandoned
> Docker Hub repository doesn't point to official GitHub repository
> -----------------------------------------------------------------
>
> Key: IGNITE-10853
> URL: https://issues.apache.org/jira/browse/IGNITE-10853
> Project: Ignite
> Issue Type: Bug
> Components: build, documentation, platforms
> Reporter: Philipp Gillé
> Priority: Major
> Attachments: 2018-12-30 apache ignite docker hub 2.PNG, 2018-12-30
> apache ignite docker hub.PNG
>
>
> According to the documentation
> (https://apacheignite.readme.io/docs/docker-deployment) the official Docker
> Hub repository is https://hub.docker.com/r/apacheignite/ignite. But the
> source repository (the GitHub repository where the Dockerfile is) points to
> https://github.com/ntikhonov/ignite, which is not the official Apache Ignite
> GitHub repository. See the attached image for this.
> You do have a Dockerfile in your official repository, see
> https://github.com/apache/ignite/tree/7989173b4d64a681fd08b7d7bcda2d26559941ae/docker/apache-ignite.
> And apparently your build process pushes the Docker image to the Docker Hub,
> so the image on the Docker Hub is actually *correct*.
> *But* there are multiple problems with this:
> 1. When looking at the Dockerfile via the Docker Hub web interface
> (https://hub.docker.com/r/apacheignite/ignite/dockerfile), it's the wrong
> Dockerfile! See the attached image for this
> 2. People might be mislead into thinking that
> https://github.com/ntikhonov/ignite is the official Ignite GitHub repository
> if they overlook that it's a fork
> 3. https://github.com/ntikhonov/ignite master branch is 2445 commits behind
> the official master. Currently it seems that the Docker Hub automatic
> building is deactivated, but if it gets activated (for building Docker
> images on each GitHub repo push) an old / wrong Docker image will be created
> on Docker Hub and it will stay wrong until your CI service pushes the correct
> one
> Related:
> - The Docker image was created in IGNITE-1046
> - The Docker image is supposed to be turned into an official Docker image in
> IGNITE-7190, but the PR has been open for one year already and seems to be
> abandoned
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
