[jira] [Updated] (IGNITE-10853) Docker Hub repository doesn't point to official GitHub repository
[ 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 >
[jira] [Commented] (IGNITE-10853) Docker Hub repository doesn't point to official GitHub repository
[ https://issues.apache.org/jira/browse/IGNITE-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731082#comment-16731082 ] Philipp Gillé commented on IGNITE-10853: P.S.: According to https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers the maintainer for the Docker image is [~ntikhonov] / [~ntikho...@apache.org], but if the JIRA activity stream in the profile is reliable then his last activity was one year ago, so maybe he isn't actively working on Ignite anymore? > 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)
[jira] [Commented] (IGNITE-7190) Docker Hub official repository deployment
[
https://issues.apache.org/jira/browse/IGNITE-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731070#comment-16731070
]
Philipp Gillé commented on IGNITE-7190:
---
[~mshonichev]: Instead of using `rm -rf /var/cache/api/*` newer Alpine versions
(since 3.3) offer a new flag that automatically disables the use of a cache:
`{{--no-cache}}`.
Source:
[https://github.com/gliderlabs/docker-alpine/blob/7945c5fceb5cbcb49dfd2a3f2bd699a1e4b19cd4/docs/usage.md#disabling-cache]
> Docker Hub official repository deployment
> -
>
> Key: IGNITE-7190
> URL: https://issues.apache.org/jira/browse/IGNITE-7190
> Project: Ignite
> Issue Type: New Feature
>Reporter: Peter Ivanov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.8
>
>
> Research possibility to integrate into Official Docker Hub Repositories.
> Use
> https://docs.docker.com/docker-hub/official_repos/#how-do-i-create-a-new-official-repository
> as start.
> https://docs.docker.com/docker-hub/official_repos
> Official Docker Hub Git Hub repository:
> * https://github.com/docker-library/official-images
> * https://github.com/docker-library/docs
> Examples (Apache Geode):
> * [Bashbrew
> file|https://github.com/docker-library/official-images/pull/3685/commits/0e34248d4b2a0ed10029577f2f50427469d6b2f4]
> * [Docs|https://github.com/docker-library/docs/pull/1062]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7190) Docker Hub official repository deployment
[
https://issues.apache.org/jira/browse/IGNITE-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731070#comment-16731070
]
Philipp Gillé edited comment on IGNITE-7190 at 12/30/18 9:06 PM:
-
[~mshonichev]: Instead of using {{rm \-rf /var/cache/api/*}} newer Alpine
versions (since 3.3) offer a new flag that automatically disables the use of a
cache: `{{--no-cache}}`.
Source:
[https://github.com/gliderlabs/docker-alpine/blob/7945c5fceb5cbcb49dfd2a3f2bd699a1e4b19cd4/docs/usage.md#disabling-cache]
was (Author: philippgille):
[~mshonichev]: Instead of using `rm -rf /var/cache/api/*` newer Alpine versions
(since 3.3) offer a new flag that automatically disables the use of a cache:
`{{--no-cache}}`.
Source:
[https://github.com/gliderlabs/docker-alpine/blob/7945c5fceb5cbcb49dfd2a3f2bd699a1e4b19cd4/docs/usage.md#disabling-cache]
> Docker Hub official repository deployment
> -
>
> Key: IGNITE-7190
> URL: https://issues.apache.org/jira/browse/IGNITE-7190
> Project: Ignite
> Issue Type: New Feature
>Reporter: Peter Ivanov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.8
>
>
> Research possibility to integrate into Official Docker Hub Repositories.
> Use
> https://docs.docker.com/docker-hub/official_repos/#how-do-i-create-a-new-official-repository
> as start.
> https://docs.docker.com/docker-hub/official_repos
> Official Docker Hub Git Hub repository:
> * https://github.com/docker-library/official-images
> * https://github.com/docker-library/docs
> Examples (Apache Geode):
> * [Bashbrew
> file|https://github.com/docker-library/official-images/pull/3685/commits/0e34248d4b2a0ed10029577f2f50427469d6b2f4]
> * [Docs|https://github.com/docker-library/docs/pull/1062]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10853) Docker Hub repository doesn't point to official GitHub repository
Philipp Gillé created IGNITE-10853: -- Summary: 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é 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 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10854) Change git URL in apply-pull-request.sh to gitbox
Roman Shtykh created IGNITE-10854: - Summary: Change git URL in apply-pull-request.sh to gitbox Key: IGNITE-10854 URL: https://issues.apache.org/jira/browse/IGNITE-10854 Project: Ignite Issue Type: Task Reporter: Roman Shtykh Assignee: Roman Shtykh -- This message was sent by Atlassian JIRA (v7.6.3#76005)
