Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CHE_DOCKER_ALWAYS__PULL__IMAGE for run portion, not just build #4197

Closed
ghost opened this issue Feb 22, 2017 · 12 comments
Closed

Add CHE_DOCKER_ALWAYS__PULL__IMAGE for run portion, not just build #4197

ghost opened this issue Feb 22, 2017 · 12 comments
Assignees
Labels
kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.

Comments

@ghost
Copy link

ghost commented Feb 22, 2017

I'd like Che not to check if there's a newer stack image on Docker Hub. However, setting CHE_DOCKER_ALWAYS__PULL__IMAGE to false in che.env does not help:

[DOCKER] latest: Pulling from eclipse/ubuntu_jdk8 
[DOCKER] Digest: sha256:69f514b226808be7d251442096bcc61d85dcb77f91f453e1cfe090a8f350c854 
[DOCKER] Status: Image is up to date for eclipse/ubuntu_jdk8:latest 

This makes it impossible to use Che in a purely offline mode.

@ghost ghost added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. and removed severity/P1 Has a major impact to usage or development of the system. labels Feb 22, 2017
@ghost
Copy link
Author

ghost commented Feb 22, 2017

Blocker for Artik. Offline mode is impossible.

@TylerJewell
Copy link

Is the che.property value (or alias) che.docker.always_pull_image? If yes, have you tried machine.docker.pull_image as well? There is some code in the core Server that assigns both values to be the same, so I wonder if this alternative version works.

https://github.com/eclipse/che/blob/9370327d4606f98a904c09a45fe9923aa6df5684/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che_aliases.properties#L49

@ghost
Copy link
Author

ghost commented Feb 22, 2017

That did not work either

@ghost
Copy link
Author

ghost commented Feb 28, 2017

It turns out this is not a bug but an enhancement request.

CHE_DOCKER_ALWAYS__PULL__IMAGE works only for build, not run.

@ghost ghost added kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system. and removed kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Feb 28, 2017
@TylerJewell TylerJewell changed the title CHE_DOCKER_ALWAYS__PULL__IMAGE does not work Add CHE_DOCKER_ALWAYS__PULL__IMAGE for run portion, not just build Apr 17, 2017
@bmicklea bmicklea added severity/P1 Has a major impact to usage or development of the system. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels May 9, 2017
@bmicklea
Copy link

bmicklea commented May 9, 2017

Increasing severity as this prevents true offline mode

@mmorhun mmorhun self-assigned this May 10, 2017
@vkuznyetsov vkuznyetsov added sprint/current status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. and removed sprint/next labels May 11, 2017
@mmorhun mmorhun added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels May 15, 2017
@mmorhun
Copy link
Contributor

mmorhun commented May 18, 2017

Done

@mmorhun mmorhun closed this as completed May 18, 2017
@mmorhun mmorhun removed the status/in-progress This issue has been taken by an engineer and is under active development. label May 18, 2017
@zanoubia
Copy link

Still having the same problem, I think, with codenvy offline mode.
Although I already downloaded the stacks I need, I can't run workspaces

docker images

REPOSITORY TAG IMAGE ID CREATED SIZE
.
.
eclipse/centos_jdk8 latest 5bd02d36ed35 5 weeks ago 877MB

And I have the following logs in instance/logs/codenvy/che-machines-logs/machineuswhc5e31bn9wnzm/machineId.logs

[DOCKER] Step 1/1 : FROM eclipse/centos_jdk8
[DOCKER]
[DOCKER] [ERROR] Failed to build image: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on <>:53: no such host
[ERROR] Docker image build failed. Image id not found in build output.

@mmorhun
Copy link
Contributor

mmorhun commented Jul 25, 2018

I would recommend you to specify the version you are using in such cases.
Just checked with nightly Che build - everything works as expected.
(I created image for workspace and didn't push it. Workspace started from it without a problem.)
Just for case, the property takes effect after Che restart.

@zanoubia
Copy link

CODENVY_VERSION: 5.22.2

@ghost
Copy link
Author

ghost commented Jul 25, 2018

@zanoubia this is Eclipse Che repository. Please, give it a try with the latest Che release.

@zanoubia
Copy link

Codenvy builds upon Eclipse Che -_-

@ghost
Copy link
Author

ghost commented Jul 25, 2018

@zanoubia Current Che version is 6.9.0-SNAPSHOT. Can you reproduce it with this version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants