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

7.0.0-RC-2.0: "Unknown component type: dockerimage" #13619

Closed
ivucica opened this issue Jun 21, 2019 · 2 comments
Closed

7.0.0-RC-2.0: "Unknown component type: dockerimage" #13619

ivucica opened this issue Jun 21, 2019 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@ivucica
Copy link

ivucica commented Jun 21, 2019

Description

Having upgraded (?) from 7.0.0-beta-5.0 by manually replacing version to 7.0.0-RC-1.0 ( see #13618), I cannot create a new workspace. When I click on "Create & Open", I get:

Unknown component type: dockerimage

Reproduction Steps

  1. Have 7.0.0-beta-5.0
  2. Replace version to 7.0.0-RC-1.0
  3. Run eclipse/che-cli:7.0.0-RC-2.0 with argument upgrade
  4. Try to create a new image.

I am not certain whether this being an upgrade matters. I'd prefer not to nuke the whole install, but I can do it if requested.

OS and version:

  • Debian 9.6

  • Linux hostname_here 4.9.0-8-amd64 Update DTD for GWT-module descriptors #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux

  • Docker:

    Client:
     Version:           18.09.1
     API version:       1.39
     Go version:        go1.10.6
     Git commit:        4c52b90
     Built:             Wed Jan  9 19:35:59 2019
     OS/Arch:           linux/amd64
     Experimental:      false
    
    Server: Docker Engine - Community
     Engine:
      Version:          18.09.1
      API version:      1.39 (minimum version 1.12)
      Go version:       go1.10.6
      Git commit:       4c52b90
      Built:            Wed Jan  9 19:02:44 2019
      OS/Arch:          linux/amd64
      Experimental:     false
    
  • Docker is running with ZFS storage backend

Diagnostics:

Not sure where to look. Happy to report back.

@ivucica
Copy link
Author

ivucica commented Jun 23, 2019

This might be because docker-based deployments seem to be no longer supported as of Che 7. See #13002 (comment)

@che-bot
Copy link
Contributor

che-bot commented Dec 30, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2019
@che-bot che-bot closed this as completed Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants