search

jenkins-x / jx

Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Cloud Native pipelines from Tekton
https://jenkins-x.io/
Apache License 2.0
4.57k stars 787 forks source link

jx create devpod -l cshap error #3693

Closed iswing closed 4 years ago

iswing commented 5 years ago

Summary

jx create devpod -l csharp
error: Invalid option: --label csharp

then i try

jx create devpod -l jx-base
Creating a DevPod of label: jx-base error: Failed to create pod Pod "myname-jx-base" is invalid: [spec.containers[0].ports[0].containerPort: Required value, spec.containers[0].volumeMounts[2].mountPath: Invalid value: "/var/run/docker.sock": must be unique]

Expected behavior

create devpod success

Actual behavior

Jx version

The output of jx version is:

NAME               VERSION
jx                 2.0.11
jenkins x platform 2.0.72
Kubernetes cluster v1.13.1
kubectl            v1.11.3
helm client        Client: v2.13.1+g618447c
git                git version 2.20.1 (Apple Git-117)
Operating System   Mac OS X 10.14 build 18A391

Jenkins type

Next Generation (Tekton + Prow)

pmuir commented 5 years ago

The valid options are

aws-cdk, dlang, go, gradle, jx-base, machine-learning, maven, maven-java11, maven-nodejs, newman, nodejs, nodejs10x, nodejs8x, promote, python, python2, python37, ruby, rust, scala, swift, terraform

pmuir commented 5 years ago

If you want to contribute dotnet support, please say

stepanselyuk commented 4 years ago

@pmuir so is there a way to use jx-base for devpod? Related https://github.com/jenkins-x/jx/issues/5026

jenkins-x-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot commented 4 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle rotten

jenkins-x-bot commented 4 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten. Provide feedback via https://jenkins-x.io/community. /close

jenkins-x-bot commented 4 years ago

@jenkins-x-bot: Closing this issue.

In response to [this](https://github.com/jenkins-x/jx/issues/3693#issuecomment-627853347): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. >Provide feedback via https://jenkins-x.io/community. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [jenkins-x/lighthouse](https://github.com/jenkins-x/lighthouse/issues/new?title=Command%20issue:) repository.