Can't open terminal in Che deployed with Che minishift addon
See original GitHub issueDescription
I’m running che on minishift via the minishift addon. I’m using the che-server:nightly docker image. I have created a workspace using the following devfile
---
specVersion: 0.0.1
name: petclinic-dev-environment
projects:
- name: petclinic
source:
type: git
location: 'git@github.com:spring-projects/spring-petclinic.git'
tools:
- name: theia-ide
type: cheEditor
id: org.eclipse.che.editor.theia:1.0.0
- name: terminal
type: chePlugin
id: che-machine-exec-plugin:0.0.1
commands:
- name: hello
actions:
- type: exec
tool: theia-ide
command: echo Hello
workdir: /projects/spring-petclinic
The workspace was created but I couldn’t start a terminal. The che pod on minishift had the following error
[GIN] 2019/01/16 - 14:08:19 | 200 | 3.161257ms | 192.168.42.1 | GET /connect
Unable to create machine exec. Cause: pods is forbidden: User "system:serviceaccount:mini-che:default" cannot list pods in the namespace "mini-che": no RBAC policy matched
Reproduction Steps
- Start che in minishift using the addon.
- Replace image with
che-server:nightly
- Create a workspace via post request to
api/devfile
with payload
---
specVersion: 0.0.1
name: petclinic-dev-environment
projects:
- name: petclinic
source:
type: git
location: 'git@github.com:spring-projects/spring-petclinic.git'
tools:
- name: theia-ide
type: cheEditor
id: org.eclipse.che.editor.theia:1.0.0
- name: terminal
type: chePlugin
id: che-machine-exec-plugin:0.0.1
commands:
- name: hello
actions:
- type: exec
tool: theia-ide
command: echo Hello
workdir: /projects/spring-petclinic
- Start the newly created workspace and try to open a new terminal.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (12 by maintainers)
Top Results From Across the Web
Minishift Quickstart - Getting Started - OKD Documentation
Deploying a Sample Application js application from the command line. To stop Minishift, use the following command:
Read more >Administration Guide Red Hat CodeReady Workspaces 1.0
The CodeReady Workspaces successfully deployed and available at <URL> message confirms that the deployment is successful. Open the OpenShift console in a ...
Read more >Configuring Minishift for use with Eclipse Che and Red Hat ...
Once minishift starts successfully, you're ready to deploy Che or CRW to the server. If minishift fails to come up, try killing and...
Read more >aandrienko/che-machine-exec - Docker Image | Docker Hub
This command activates openshift context to use minishift instance: To deploy Eclipse CHE You can use deploy_che.sh script. Move to deploy_che.sh script: cd...
Read more >CHANGELOG.md · fef7cc44e66cb24b82df42dbe8c819db65915568 ...
disableDnsResolver=true to vert.x run / debug commands #9611 (ibuziuk) ... make KC configuration before CHE start in case of deploy to OS #9181...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jarifibrahim Thanks. I can easily set up my own
minishift
installation. But this issue should be prioritized to be taken in the sprint ofche-platform
orche-osio
team.Worked for me too, and even on a fresh installation I had to reset the minishift installation!