garden-io / garden

Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same configuration and workflows at every step of the process. Speed up your builds and test runs via shared result caching
https://garden.io
Mozilla Public License 2.0
3.39k stars 275 forks source link

Crash: self-signed certificate in certificate chain #6504

Open scott-rogowski-virta opened 1 month ago

scott-rogowski-virta commented 1 month ago

Crash report

Hi, I'm trialing Garden for my company, Virta Health. I'm using my personal Github to avoid installing Garden into our company Github before trialing and receiving permission.

I'm following the quickstart guide and cannot run garden dev. When I do so, I'm getting a self-signed certificate error. We have Netskope installed on our work laptops and that's unfortunately not going to change.

Error message

─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── 🌳  garden dev 🌳  ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Good afternoon! Welcome to the Garden interactive development console.

Here you can build, deploy, test and run anything in your project, start code syncing, stream live logs and more.

Use the command line below to enter Garden commands. Type help to get a full list of commands.
Use up/down arrow keys to scroll through your command history.

Unable to load Garden project found at /Users/scott/quickstart-example: RequestError: self-signed certificate in certificate chain
Garden server has successfully started at port 9777

Encountered an unexpected Garden error. This is likely a bug 🍂

You can help by reporting this on GitHub: https://github.com/garden-io/garden/issues/new?labels=bug,crash&template=CRASH.md&title=Crash%3A%20self-signed%20certificate%20in%20certificate%20chain

Please attach the following information to the bug report after making sure that the error message does not contain sensitive information:

RequestError: self-signed certificate in certificate chain
    at ClientRequest.<anonymous> (file:///Users/scott/Library/Application%20Support/io.garden.garden/1727819429-UZmo7bu.r/rollup/garden.mjs:228501:103)
    at Object.onceWrapper (node:events:635:26)
    at ClientRequest.emit (node:events:532:35)
    at ClientRequest.emit (node:domain:488:12)
    at emitErrorEvent (node:_http_client:103:11)
    at TLSSocket.socketErrorListener (node:_http_client:506:5)
    at TLSSocket.emit (node:events:520:28)
    at TLSSocket.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34)
    at TLSSocket.emit (node:events:520:28)
    at TLSSocket.emit (node:domain:488:12)
    at TLSSocket._finishInit (node:_tls_wrap:1078:8)
    at ssl.onhandshakedone (node:_tls_wrap:864:12)
    at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17)

See .garden/error.log for detailed error message

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── 🌼 🌸 🌷 🌺 🌻  ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
 🌸  Initializing...

What did you do?

So far, I've followed this issue https://github.com/garden-io/garden/issues/1217 which led to this closed issue https://github.com/garden-io/garden/issues/1478. I'm wondering if, since that issue was closed, another option might be available? Garden is, on paper, the most promising of the tools we are evaluating.

Your environment

Frequency

Everytime

Workaround

N/A

Additional context

N/A

eysi09 commented 1 month ago

Hi @scott-rogowski-virta

Do you have the same issue if you just run garden deploy (and thereby do not start the Garden server)?

eysi09 commented 3 weeks ago

Hi @scott-rogowski-virta

Just wanted to check in again and see if you were still having this issue?