Nocalhost is Cloud Native Dev Environment.

Overview

api-docker nhctl Go Report Card LICENSE


Most productive way to build cloud-native applications.

Nocalhost

The term Nocalhost originates from No Local, which is a cloud-native development tool based on IDE, provides realtime cloud native application developing experience.

When developing cloud-based application in Nocalhost, any code changes can immediately take effects in remote side, and there is no need to rebuild a new image. This can shorten the entire development feedback loops and massively improve R&D efficiency.

In order to give you a better understanding of Nocalhost, it is recommended that you read our blog post Nocalhost - Refine Cloud Native Dev Environment

Nocalhost

Key Features

IDE Supports

Nocalhost provides easy-to-use IDE extension for JetBrains and VSCode. These extension will enable developer to develop and debug cloud-based application in their local machine.

Start cloud-native application development in one click

No need to config complex dev environments in your local machine anymore. Nocalhost helps you to connect to any Kubernetes environment in one click.

See code change under a second

automatically synchronize the code to container every time you make a change. Nocalhost eliminate the submit, building and pushing cycles, significantly speed up the feedback loop of development, so you see change in under a second.

Isolated development space

Every team member can enjoy their own independent development space to ensure that they are not disturbed by others.

Getting Started

Documentation

Full documentation is available on the Nocalhost

Community

  • Slack: Nocalhost Slack Channel
  • WeChat: Scan the QR Code to add CODING assistance with note "Nocalhost", assistance will add you into our WeChat group

nocal-host-wechat

Talks and Conferences

Engagement Link
📹   Nocalhost Youtube https://www.youtube.com/channel/UC2QC6HvFG8zOtFRvvMzcAUw

Changelogs

Check our Changelogs

Contributing

Check out CONTRIBUTING to see how to develop with Nocalhost.

Code of Conduct

Nocalhost adopts CNCF Code of Conduct

License

Nocalhost is Apache 2.0 licensed

Roadmap

See ROADMAP

Comments
  • vscode nocalhost 不能正常使用

    vscode nocalhost 不能正常使用

    What happened: image 如图点击 add cluster ,添加完成后,会提示 unable to connect。 我查看日志,发现是读取ca.pem文件路径不对(以前第一次使用比较久以前的版本是可以的,现在忘了具体是哪个版本了),于是我通过paste as text 添加,这一步我修改了我的默认配置中的ca文件目录为绝对路径如/users/nero/.kube/ca.pem,然后 连接成功了,但是k8s中的所有资源都不能正常加载。。。 image 如 我本身kubectl 可以正常使用: image

    我发现的问题:

    1. add cluster 添加时,会存在ca.pem配置文件路径问题
    2. 不知道啥原因,连接上k8s api server后,功能使用异常

    Environment:

    • Macos 11.4 (20F71)
    • nhctl version v0.5.1
    • kubectl version

    Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.10", GitCommit:"98d5dc5d36d34a7ee13368a7893dcb400ec4e566", GitTreeState:"clean", BuildDate:"2021-04-15T03:20:25Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}

    opened by nerocho 20
  • Remote Debug is beening in Waiting pod to start...

    Remote Debug is beening in Waiting pod to start...

    我的开发工具是IntelliJ Idea,使用了nocalhost来调试远程k8s上的应用,点击了Remote Debug以后,控制台输出日志,显示一直处于Waiting pod to start...,Dev Config是参照文档中配置的,配置是 image 。 debug.sh配置是 image 。 控制台日志是 image 这是什么问题呢?

    help wanted 
    opened by edewofenwen 9
  • Development env  Support envFrom

    Development env Support envFrom

    What would you like to be added: I wish Development env Support envFrom

    Why is this needed: The environment variables we use online are all in configmap, That's too much. Manual migration to Env is too complicated for me.

    opened by leonharetd 7
  • no Auth Provider found for name

    no Auth Provider found for name "azure"

    What would you like to be added: add support for auth provider for azure ad

    Why is this needed: our cluster auth is managed by azure ad, we try to connect cluster, it give error as below: Please check if your cluster or kubeconfig is valid, Error: : no Auth Provider found for name "azure"

    opened by jtechtips 6
  • nhctl exec don't support app deployed as statefulset

    nhctl exec don't support app deployed as statefulset

    What happened: My app workload type is statefulset. I use goland and nocalhost plugin to start remote dev. When I click the button "Run"(nocalhost run config), the comand is like "nhctl exec test --deployment test-my-operator --controller-type statefulset --command /bin/zsh --command -c --command "go run cmd/my-operator/ma in.go" --kubeconfig ~/.nh/intellij-plugin/kubeConfigs/d9ca5ba8-5a30-4dec-a2c9-d8ba313f0218_config --namespace default ",and the return error is " deployments.apps "test-my-operator" not found"

    What you expected to happen: No error returned.

    How to reproduce it (as minimally and precisely as possible): App workload type is statefulset and start remote dev by click "Run"(run configured as nocalhost need)

    Anything else we need to know?: The func ListPodsByDeployment only handle deployment resource.

    Environment:

    • OS (e.g: Macos 10.15.5 (19F96) or Windows 10): macOS 11.5.1
    • nhctl version (use nchtl version command): 0.5.1(0.5.4 is also the same)
    • helm version (use helm version command): none
    • kubectl version (use kubectl version command):
    • Others: nocalhost plugin version 0.5.1-211
    • IDE: GoLand 2021-01
    opened by von1994 6
  • nocalhost kubeconfig not support gcp

    nocalhost kubeconfig not support gcp

    What happened: I create cluster from nocalhost web ui, then i add gcp kube config , it reported "KubeConfig parse error"

    What you expected to happen: add gcp kubeconfig then add gcp cluster

    How to reproduce it (as minimally and precisely as possible):

    Anything else we need to know?:

    Environment:

    • OS (e.g: Macos 10.15.5 (19F96) or Windows 10):
    • nhctl version (use nchtl version command):
    • helm version (use helm version command):
    • kubectl version (use kubectl version command):
    • Others:
    opened by LuckyDogg 6
  • nocalhost dev deployment is missing privileged config

    nocalhost dev deployment is missing privileged config

    What happened:

    I am using nocalhost to debug kube-proxy.

    I used the Edit Manifest to look at the yaml of kube-proxy, and there are privileges:

    ......
                containers:
                    - command:
                        - /usr/local/bin/kube-proxy
                        - --config=/var/lib/kube-proxy/config.conf
                        - --hostname-override=$(NODE_NAME)
                        - --feature-gates=TopologyAwareHints=true
                      env:
                        - name: NODE_NAME
                          valueFrom:
                            fieldRef:
                                apiVersion: v1
                                fieldPath: spec.nodeName
                      image: k8s.gcr.io/kube-proxy:v1.21.8
                      imagePullPolicy: IfNotPresent
                      name: kube-proxy
                      resources: {}
                      securityContext:
                        privileged: true        <--------------------------------- here!!!
    ......
    

    However, the generated dev deployment, without privileged. I use the command kubectl -n kube-system get deployment.apps/daemon-set-generated-deploy-kube-proxy -oyaml to get dev deployment yaml:

    (You cannot find privileged here)

    apiVersion: apps/v1
    kind: Deployment
    metadata:
      annotations:
        deployment.kubernetes.io/revision: "1"
      creationTimestamp: "2022-01-11T12:07:06Z"
      generation: 1
      labels:
        nocalhost.dev.workload.ignored: "true"
      name: daemon-set-generated-deploy-kube-proxy
      namespace: kube-system
      resourceVersion: "28962130"
      selfLink: /apis/apps/v1/namespaces/kube-system/deployments/daemon-set-generated-deploy-kube-proxy
      uid: f61d9b0a-1e6a-4d7e-a885-186617a1d452
    spec:
      progressDeadlineSeconds: 600
      replicas: 1
      revisionHistoryLimit: 10
      selector:
        matchLabels:
          k8s-app: kube-proxy
      strategy:
        rollingUpdate:
          maxSurge: 25%
          maxUnavailable: 25%
        type: RollingUpdate
      template:
        metadata:
          creationTimestamp: null
          labels:
            k8s-app: kube-proxy
        spec:
          affinity:
            nodeAffinity:
              requiredDuringSchedulingIgnoredDuringExecution:
                nodeSelectorTerms:
                - matchExpressions:
                  - key: node-role.kubernetes.io/edge
                    operator: DoesNotExist
                  - key: node-role.kubernetes.io/agent
                    operator: DoesNotExist
          containers:
          - command:
            - /bin/sh
            - -c
            - tail -f /dev/null
            env:
            - name: NODE_NAME
              valueFrom:
                fieldRef:
                  apiVersion: v1
                  fieldPath: spec.nodeName
            image: nocalhost-docker.pkg.coding.net/nocalhost/dev-images/golang:zsh
            imagePullPolicy: Always
            name: nocalhost-dev
            resources:
              limits:
                cpu: "2"
                memory: 4Gi
              requests:
                cpu: "1"
                memory: 2Gi
            terminationMessagePath: /dev/termination-log
            terminationMessagePolicy: File
            volumeMounts:
            - mountPath: /var/lib/kube-proxy
              name: kube-proxy
            - mountPath: /run/xtables.lock
              name: xtables-lock
            - mountPath: /lib/modules
              name: lib-modules
              readOnly: true
            - mountPath: /var/syncthing
              name: nocalhost-syncthing
              subPath: syncthing
            - mountPath: /var/syncthing/secret
              name: nocalhost-syncthing-secret
            - mountPath: /home/nocalhost-dev
              name: nocalhost-shared-volume
            workingDir: /home/nocalhost-dev
          - args:
            - rc-service sshd restart && unset STGUIADDRESS && cp /var/syncthing/secret/*
              /var/syncthing/ && /bin/entrypoint.sh && /bin/syncthing -home /var/syncthing
            command:
            - /bin/sh
            - -c
            image: nocalhost-docker.pkg.coding.net/nocalhost/public/nocalhost-sidecar:sshversion
            imagePullPolicy: Always
            name: nocalhost-sidecar
            resources:
              limits:
                cpu: "1"
                memory: 1Gi
              requests:
                cpu: 100m
                memory: 50Mi
            terminationMessagePath: /dev/termination-log
            terminationMessagePolicy: File
            volumeMounts:
            - mountPath: /var/syncthing
              name: nocalhost-syncthing
              subPath: syncthing
            - mountPath: /var/syncthing/secret
              name: nocalhost-syncthing-secret
            - mountPath: /home/nocalhost-dev
              name: nocalhost-shared-volume
            workingDir: /home/nocalhost-dev
          dnsPolicy: ClusterFirst
          hostNetwork: true
          nodeSelector:
            kubernetes.io/os: linux
          priorityClassName: system-node-critical
          restartPolicy: Always
          schedulerName: default-scheduler
          securityContext: {}
          serviceAccount: kube-proxy
          serviceAccountName: kube-proxy
          terminationGracePeriodSeconds: 30
          tolerations:
          - key: CriticalAddonsOnly
            operator: Exists
          - operator: Exists
          volumes:
          - configMap:
              defaultMode: 420
              name: kube-proxy
            name: kube-proxy
          - hostPath:
              path: /run/xtables.lock
              type: FileOrCreate
            name: xtables-lock
          - hostPath:
              path: /lib/modules
              type: ""
            name: lib-modules
          - emptyDir: {}
            name: nocalhost-syncthing
          - name: nocalhost-syncthing-secret
            secret:
              defaultMode: 448
              items:
              - key: config.xml
                mode: 448
                path: config.xml
              - key: cert.pem
                mode: 448
                path: cert.pem
              - key: key.pem
                mode: 448
                path: key.pem
              secretName: kube-proxy-daemonset-nocalhost-syncthing-secret
          - name: nocalhost-shared-volume
            persistentVolumeClaim:
              claimName: default.application-1641888119229698000
    status:
      availableReplicas: 1
      conditions:
      - lastTransitionTime: "2022-01-11T12:07:10Z"
        lastUpdateTime: "2022-01-11T12:07:10Z"
        message: Deployment has minimum availability.
        reason: MinimumReplicasAvailable
        status: "True"
        type: Available
      - lastTransitionTime: "2022-01-11T12:07:06Z"
        lastUpdateTime: "2022-01-11T12:07:10Z"
        message: ReplicaSet "daemon-set-generated-deploy-kube-proxy-c5fb794bf" has successfully
          progressed.
        reason: NewReplicaSetAvailable
        status: "True"
        type: Progressing
      observedGeneration: 1
      readyReplicas: 1
      replicas: 1
      updatedReplicas: 1
    

    This will make my dev container unprivileged and will not be able to create iptables rules!!!

    By the way, I manually adding privileges to dev deployment will solve this problem.

    opened by Poorunga 5
  • why windows defender keeping alert ?

    why windows defender keeping alert ?

    What happened: See the picture:

    image

    Whether the windows defender let it go or not, it would always keep alerts.

    image

    Environment:

    • OS (e.g: Macos 10.15.5 (19F96) or Windows 10): Windows 10
    • nhctl version (use nchtl version command): maybe install by vscode?
    • helm version (use helm version command): not yet
    • kubectl version (use kubectl version command): cannot connect it.
    • Others:
    opened by zhu733756 5
  • nocalhost can not be installed successfully on k3s

    nocalhost can not be installed successfully on k3s

    What happened: I use a k3s cluster and want to install nocalhost. It doesn't work with nocalhost-api CrashLoopBackOff.


    The output of kubectl get pod -nnocalhost -owide:

    NAME                             READY   STATUS             RESTARTS   AGE   IP           NODE              NOMINATED NODE   READINESS GATES
    svclb-nocalhost-web-7nkvh        1/1     Running            0          73s   10.42.1.9    node-ccf0ed90     <none>           <none>
    svclb-nocalhost-web-fqms9        1/1     Running            0          73s   10.42.0.16   master-d39b1dd5   <none>           <none>
    svclb-nocalhost-web-77849        1/1     Running            0          73s   10.42.2.7    node-2ffe5da9     <none>           <none>
    nocalhost-web-6f8f65d48f-xvzwt   1/1     Running            0          73s   10.42.2.8    node-2ffe5da9     <none>           <none>
    nocalhost-api-7bdd895d99-tbthc   0/1     CrashLoopBackOff   3          73s   10.42.1.8    node-ccf0ed90     <none>           <none>
    

    The log of nocalhost-api pod:

    # kubectl logs -f -nnocalhost nocalhost-api-7bdd895d99-tbthc
    panic: runtime error: invalid memory address or nil pointer dereference
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0xb7d260]
    
    goroutine 1 [running]:
    nocalhost/pkg/nocalhost-api/pkg/log.Errorf(...)
            /opt/src/pkg/nocalhost-api/pkg/log/logger.go:121
    nocalhost/internal/nocalhost-api/model.openDB(0xc000594118, 0x4, 0xc000594130, 0x4, 0xc000476460, 0x16, 0xc0005940f0, 0x9, 0xc00034fd80)
            /opt/src/internal/nocalhost-api/model/init.go:53 +0x4c0
    nocalhost/internal/nocalhost-api/model.Init(0x1959b60)
            /opt/src/internal/nocalhost-api/model/init.go:34 +0x14d
    nocalhost/pkg/nocalhost-api/napp.New(0xc0003cc340, 0x17)
            /opt/src/pkg/nocalhost-api/napp/app.go:62 +0x4e
    main.main()
            /opt/src/cmd/nocalhost-api/nocalhost-api.go:74 +0x319
    

    What you expected to happen: nocalhost install successfully.

    How to reproduce it (as minimally and precisely as possible):

    Anything else we need to know?: My k3s cluster is using containerd instand of docker.

    Environment:

    • OS (e.g: Macos 10.15.5 (19F96) or Windows 10): ubuntu 18.04.5 LTS
    • nhctl version (use nchtl version command): v0.2.1 (defe9f2f33fda0bed2eb9791450eaa2f7badc7ed)
    • helm version (use helm version command):
    version.BuildInfo{Version:"v3.1.2", GitCommit:"d878d4d45863e42fd5cff6743294a11d28a9abce", GitTreeState:"clean", GoVersion:"go1.13.8"}
    
    • kubectl version (use kubectl version command):
    Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.1", GitCommit:"c4d752765b3bbac2237bf87cf0b1c2e307844666", GitTreeState:"clean", BuildDate:"2020-12-23T02:22:53Z", GoVersion:"go1.15.6", Compiler:"gc", Platform:"linux/amd64"}
    Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3-k3s.2", GitCommit:"e7e6a3c4e9a7d80b87793612730d10a863a25980", GitTreeState:"clean", BuildDate:"2019-11-18T18:31:23Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}
    
    • Others:
    # kubectl get node
    NAME              STATUS   ROLES    AGE   VERSION
    node-2ffe5da9     Ready    <none>   29h   v1.16.3-k3s.2
    node-ccf0ed90     Ready    <none>   29h   v1.16.3-k3s.2
    master-d39b1dd5   Ready    master   29h   v1.16.3-k3s.2
    
    opened by Pancongwen 5
  • could  give more useful information about config.yaml lint?

    could give more useful information about config.yaml lint?

    What would you like to be added: when i start dev mode,error happens:

    [cmd] /Users/owen/.nh/bin/nhctl dev associate default.application --local-sync /Users/owen/woqu/qfushion/dock-template --controller-type Deployment --deployment dock --container dock --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion [name: dock serviceType: deployment] Load nocalhost svc config from local fail, err: [Local config loaded, but no valid config found] [cmd] /Users/owen/.nh/bin/nhctl dev containers default.application --controller-type Deployment --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion --deployment dock ["dock"] [cmd] /Users/owen/.nh/bin/nhctl dev associate default.application --local-sync /Users/owen/woqu/qfushion/dock-template --controller-type Deployment --deployment dock --container dock --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion [name: dock serviceType: deployment] Load nocalhost svc config from local fail, err: [Local config loaded, but no valid config found] [cmd] /Users/owen/.nh/bin/nhctl dev containers default.application --controller-type Deployment --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion --deployment dock ["dock"] [cmd] /Users/owen/.nh/bin/nhctl dev associate default.application --local-sync /Users/owen/woqu/qfushion/dock-template --controller-type Deployment --deployment dock --container dock --kubeconfig /Users/owen/.nh/intellij-plugin/kubeConfigs/ed9a7ff5-b0de-4357-8a4a-a90d1e4659fd_config --namespace qfusion [name: dock serviceType: deployment] Load nocalhost svc config from local fail, err: [Local config loaded, but no valid config found]

    so,could we add more useful information for invalid config yaml file?

    Why is this needed: i do not know what errors i writen in the config yaml file,

    opened by acguokailin 4
  • A large number of zombie processes lead to

    A large number of zombie processes lead to "fork: Resource temporarily unavailable"

    What happened: use GoLand 2021.3.3 + plugin Nocalhost 0.6.15-213

    $ ps -A -ostat,ppid,pid,command|grep nhctl
    Ss   11768     1 10:41上午   1:29.71 /Users/shareit/.nh/bin/nhctl daemon start
    Z    13060 11768 10:42上午   0:00.00 (nhctl)
    Z    13958 11768 10:44上午   0:00.00 (nhctl)
    Z    14968 11768 10:46上午   0:00.00 (nhctl)
    Z    16024 11768 10:48上午   0:00.00 (nhctl)
    Z    16935 11768 10:50上午   0:00.00 (nhctl)
    Z    17889 11768 10:52上午   0:00.00 (nhctl)
    Z    18933 11768 10:54上午   0:00.00 (nhctl)
    Z    19992 11768 10:56上午   0:00.00 (nhctl)
    Z    20981 11768 10:58上午   0:00.00 (nhctl)
    Z    21884 11768 11:00上午   0:00.00 (nhctl)
    Z    22817 11768 11:02上午   0:00.00 (nhctl)
    Z    23755 11768 11:04上午   0:00.00 (nhctl)
    Z    24737 11768 11:06上午   0:00.00 (nhctl)
    Z    25668 11768 11:08上午   0:00.00 (nhctl)
    Z    27403 11768 11:10上午   0:00.00 (nhctl)
    Z    28383 11768 11:12上午   0:00.00 (nhctl)
    Z    29355 11768 11:14上午   0:00.00 (nhctl)
    Z    30608 11768 11:16上午   0:00.00 (nhctl)
    Z    31958 11768 11:18上午   0:00.00 (nhctl)
    Z    32907 11768 11:20上午   0:00.00 (nhctl)
    Z    33927 11768 11:22上午   0:00.00 (nhctl)
    Z    35035 11768 11:24上午   0:00.00 (nhctl)
    Z    36139 11768 11:26上午   0:00.00 (nhctl)
    Z    37296 11768 11:28上午   0:00.00 (nhctl)
    Z    38334 11768 11:30上午   0:00.00 (nhctl)
    Z    39320 11768 11:32上午   0:00.00 (nhctl)
    Z    40274 11768 11:34上午   0:00.00 (nhctl)
    Z    41315 11768 11:36上午   0:00.00 (nhctl)
    ......
    

    Every once in a while, a zombie process will be generated. After a long time, a large number of zombie processes will be generated, which will lead to exhaustion of system resources. For example, an error "fork: Resource temporarily unavailable" will be reported when using the terminal.

    Anything else we need to know?:

    in ~/.nh/nhctl/logs/nhctl.log file, all nhctl zombie processes have logs like this:

    Mar  4 11:12:16	[INFO]	Starting daemon server...	{"PID": "28383", "PPID": "11768", "VERSION": "v0.6.15", "COMMIT": "8887e8045ee5485f7adc0469354e9d9323a13698", "BRANCH": "HEAD", "ARGS": "/Users/shareit/.nh/bin/nhctl daemon start --sudo true", "APP": "daemon-server", "fn": "/Users/runner/work/nocalhost/nocalhost/internal/nhctl/daemon_server/daemon.go", "line": 64}
    Mar  4 11:12:16	[FATAL]	, err: Failed to start daemon server with sudo
    nocalhost/internal/nhctl/daemon_server.StartDaemon
    	/Users/runner/work/nocalhost/nocalhost/internal/nhctl/daemon_server/daemon.go:71
    nocalhost/cmd/nhctl/cmds.glob..func16
    	/Users/runner/work/nocalhost/nocalhost/cmd/nhctl/cmds/daemon_start.go:33
    github.com/spf13/cobra.(*Command).execute
    	/Users/runner/work/nocalhost/nocalhost/vendor/github.com/spf13/cobra/command.go:860
    github.com/spf13/cobra.(*Command).ExecuteC
    	/Users/runner/work/nocalhost/nocalhost/vendor/github.com/spf13/cobra/command.go:974
    github.com/spf13/cobra.(*Command).Execute
    	/Users/runner/work/nocalhost/nocalhost/vendor/github.com/spf13/cobra/command.go:902
    nocalhost/cmd/nhctl/cmds.Execute
    	/Users/runner/work/nocalhost/nocalhost/cmd/nhctl/cmds/root.go:149
    main.main
    	/Users/runner/work/nocalhost/nocalhost/cmd/nhctl/nhctl.go:13
    runtime.main
    	/Users/runner/hostedtoolcache/go/1.16.7/x64/src/runtime/proc.go:225
    runtime.goexit
    	/Users/runner/hostedtoolcache/go/1.16.7/x64/src/runtime/asm_arm64.s:1130	{"PID": "28383", "PPID": "11768", "VERSION": "v0.6.15", "COMMIT": "8887e8045ee5485f7adc0469354e9d9323a13698", "BRANCH": "HEAD", "ARGS": "/Users/shareit/.nh/bin/nhctl daemon start --sudo true", "APP": "daemon-server", "fn": "/Users/runner/work/nocalhost/nocalhost/cmd/nhctl/cmds/install.go", "line": 209}
    
    

    Environment:

    • OS: Macos 11.6 (20G165) MacBook Air (M1, 2020)
    • nhctl version (use nchtl version command): nhctl: Nocalhost CLI Version: v0.6.15 Branch: HEAD Git commit: 8887e8045ee5485f7adc0469354e9d9323a13698 Built time: Wed Jan 19 02:15:09 2022 Built OS/Arch: darwin/arm64 Built Go version: go1.16.7
    • helm version (use helm version command): version.BuildInfo{Version:"v3.7.2", GitCommit:"663a896f4a815053445eec4153677ddc24a0a361", GitTreeState:"clean", GoVersion:"go1.17.3"}
    • kubectl version (use kubectl version command): Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:08:39Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"darwin/arm64"} Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.9-r0-CCE20.8.1.3.B001-17.36.5",
      GitCommit:"d61c11191a704802f93e5d86877a8fcffe208d58", GitTreeState:"clean", BuildDate:"2020-10-16T09:38:58Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
    • Others: GoLand 2021.3.3 Goland plugin Nocalhost 0.6.15-213
    opened by thinkhp 4
  • fix sidecar sshd failed

    fix sidecar sshd failed

    What this PR does / why we need it:

    Special notes for your reviewer:

    If applicable:

    • [ ] this PR contains documentation
    • [ ] this PR contains unit tests
    • [ ] this PR has been tested for backwards compatibility
    opened by shy-Xu 3
  • Cannot start sshd in sidecar container

    Cannot start sshd in sidecar container

    What happened:

    Sidecar container started failed.

    hIGFWfsjZV

    What you expected to happen:

    How to reproduce it (as minimally and precisely as possible):

    install harbor-helm (https://github.com/goharbor/harbor-helm) and try to develop harbor-core

    Anything else we need to know?:

    Environment:

    • OS (e.g: Macos 10.15.5 (19F96) or Windows 10): macOS 12.5.1 (21G83)
    • nhctl version (use nchtl version command):
    • helm version (use helm version command):
    • kubectl version (use kubectl version command):
    • Others:
    opened by jack230230 2
Releases(v0.6.18)
Owner
Nocalhost
Nocalhost is Cloud Native Development Environment
Nocalhost
Cloud-native way to provide elastic Jupyter Notebook services on Kubernetes

elastic-jupyter-operator: Elastic Jupyter on Kubernetes Kubernetes 原生的弹性 Jupyter 即服务 介绍 为用户按需提供弹性的 Jupyter Notebook 服务。elastic-jupyter-operator 提供以下特性

TKEStack 132 Sep 21, 2022
A Cloud Native Buildpack for Go

The Go Paketo Buildpack provides a set of collaborating buildpacks that enable the building of a Go-based application.

Paketo Buildpacks 56 Sep 13, 2022
cloud-native local storage management system

Open-Local是由多个组件构成的本地磁盘管理系统,目标是解决当前 Kubernetes 本地存储能力缺失问题。通过Open-Local,使用本地存储会像集中式存储一样简单。

null 289 Sep 21, 2022
Elkeid is a Cloud-Native Host-Based Intrusion Detection solution project to provide next-generation Threat Detection and Behavior Audition with modern architecture.

Elkeid is a Cloud-Native Host-Based Intrusion Detection solution project to provide next-generation Threat Detection and Behavior Audition with modern architecture.

Bytedance Inc. 1.4k Sep 27, 2022
A Cloud Native Buildpack that contributes SDKMAN and uses it to install dependencies like the Java Virtual Machine

gcr.io/paketo-buildpacks/sdkman A Cloud Native Buildpack that contributes SDKMAN and uses it to install dependencies like the Java Virtual Machine. Be

Daniel Mikusa 1 Jan 8, 2022
A Cloud Native Buildpack that provides the Open Liberty runtime

gcr.io/paketo-buildpacks/open-liberty The Paketo Open Liberty Buildpack is a Cloud Native Buildpack that contributes Open Liberty for Java EE support.

Paketo Buildpacks 5 Jul 7, 2022
cloneMAP: cloud-native Multi-Agent Platform

cloneMAP: cloud-native Multi-Agent Platform cloneMAP is a multi-agent platform (MAP) that is designed to run in a cloud environment based on Kubernete

RWTH Aachen University, Institute for Automation of Complex Power Systems 3 Aug 31, 2022
A Cloud Native Buildpack that contributes the Syft CLI which can be used to generate SBoM information

gcr.io/paketo-buildpacks/syft The Paketo Syft Buildpack is a Cloud Native Buildpack that contributes the Syft CLI which can be used to generate SBoM i

Paketo Buildpacks 3 Sep 23, 2022
TurtleDex is a decentralized cloud storage platform that radically alters the landscape of cloud storage.

TurtleDex is a decentralized cloud storage platform that radically alters the landscape of cloud storage. By leveraging smart contracts, client-side e

TurtleDev 18 Feb 17, 2021
Contentrouter - Protect static content via Firebase Hosting with Cloud Run and Google Cloud Storage

contentrouter A Cloud Run service to gate static content stored in Google Cloud

G. Hussain Chinoy 0 Jan 2, 2022
An edge-native container management system for edge computing

SuperEdge is an open source container management system for edge computing to manage compute resources and container applications in multiple edge regions. These resources and applications, in the current approach, are managed as one single Kubernetes cluster. A native Kubernetes cluster can be easily converted to a SuperEdge cluster.

SuperEdge 851 Sep 19, 2022
Lightweight Cloud Instance Contextualizer

Flamingo Flamingo is a lightweight contextualization tool that aims to handle initialization of cloud instances. It is meant to be a replacement for c

Tamer Tas 36 Jun 18, 2022
Go language interface to Swift / Openstack Object Storage / Rackspace cloud files (golang)

Swift This package provides an easy to use library for interfacing with Swift / Openstack Object Storage / Rackspace cloud files from the Go Language

Nick Craig-Wood 292 Jun 30, 2022
The extensible SQL interface to your favorite cloud APIs.

The extensible SQL interface to your favorite cloud APIs.

Turbot 2.4k Sep 22, 2022
Terraform provider for HashiCorp Cloud Platform.

HashiCorp Cloud Platform (HCP) Terraform Provider Requirements Terraform >= 0.12.x Go >= 1.14 Building The Provider Clone the repository Enter the rep

HashiCorp 27 Jul 4, 2022
The Cloud Posse Terraform Provider for various utilities (E.g. deep merging)

terraform-provider-utils Terraform provider to add additional missing functionality to Terraform This project is part of our comprehensive "SweetOps"

Cloud Posse 64 Sep 22, 2022
Cloud cost estimates for Terraform in your CLI and pull requests 💰📉

Infracost shows cloud cost estimates for Terraform projects. It helps developers, devops and others to quickly see the cost breakdown and compare different options upfront.

Infracost 7.9k Sep 25, 2022
Google Cloud Client Libraries for Go.

Google Cloud Client Libraries for Go.

Google APIs 3k Sep 23, 2022
Fleex allows you to create multiple VPS on cloud providers and use them to distribute your workload.

Fleex allows you to create multiple VPS on cloud providers and use them to distribute your workload. Run tools like masscan, puredns, ffuf, httpx or anything you need and get results quickly!

null 169 Sep 11, 2022