David
David
It works for some build stages, but extremely slow, and finally it leads to issue #22. ``` # Build stage 1 FROM registry/sdk-image:latest AS builder // Image with LLVM project...
Seems `vctl build` will put the whole volume of vctl-builder on a RAM disk?
And I can see an vctl-builder persistent storage, but seems builder doesn't use it.
And more, if builder unexpected exit while building, the vm will not stop properly, and if run `vctl system stop` error message ``` Stop virtual machine vctl-builder-b7cce09d ... ERROR failed...
@mikeroySoft Actually I am writing a compiler with LLVM, LLVM is big you know.
@wswfc Sorry I can't give you the base Image, but https://hub.docker.com/r/nwtgck/llvm-clang/tags maybe you can try. It has 9.17G compressed size.
Yeah, vscode.dev requires Web Extensions, that many existing extensions haven't supported yet, including ours, as they need to be implemented using browserify packages. If code-server supported the Filesystem API like...
Uncheck this option to solve the problem:
It seems that the PATH is being overridden by either the Okteto VSCode extension (Remote-Kubernetes) or the code-server. There are no issues with the standalone Okteto environment.
Sorry for the delayed response. In the integrated terminal of the remote window, the PATH variable is being overridden. Here is my $PATH variable: Here is the one in the...