code-server | VS Code in the browser

@oakad Thank you for the suggesting and pointing to upgrade the libstdc++ on the remote side.

• The host that I was using was RPi 3B Debian(Jessie). I tried to upgrade the remote box on vs code and the

sudo apt-get update

• This thread addressed libstdc++.so.6: version `GLIBCXX_3.4.22' not found issue

So tried

Open the "run and debug" tab from the sidebar and at the bottom you would find a section called "breakpoints".

Under that, uncheck "raised exceptions" and "user uncaught exceptions".

The above can be achieved using multiple ways in AWS ECS. The basic requirements for such systems are to launch and terminate containers on the fly while persisting the changes in the files. (I will focus on launching the containers)

The task can be easily achieved using AWS SDKs, Using a base task definition. AWS SDK allows starting tasks with overrides on the base task definition.

E.G. If task definition has a memory of 2GB then the SDK can override the memory to parameterised value while launching a task from task def.

Refer to the boto3 (AWS SDK for Python) docs.

https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ecs.html#ECS.Client.run_task

Now that we know how to run custom tasks with python SDK (on demand). The overall flow for your application is your API calling AWS lambda function whit parameters to spin up and wait to keep checking task status and update and rout traffic to it once the status is healthy.

1. API calls AWS lambda functions with parameters
2. Lambda function using AWS SDK create a new task with overrides from base task definition. (assuming the base task definition already exists)
3. Keep checking the status of the new task in the same function call and set a flag in your database for your front end to be able to react to it.
4. Once the status is healthy you can add a rule in the application load balancer using AWS SDK to route traffic to the IP without exposing the IP address to the end client (AWS application load balancer can get expensive, I'll advise using Nginx or HAProxy on ec2 to manage dynamic routing)

Ensure your Image is lightweight, and the startup times are less than 15 mins as lambda cannot execute beyond that. If that's the case create a microservice for launching ad-hoc containers and hosting them on EC2

If you looking for infrastructure provisioning terraform is the way to go. It has a learning curve so recommend it as a secondary option.

Terraform is popular for parametrising using variables and it can be plugged in easily as a backend for an API. The flow of your application still remains the same from step 1, but instead of AWS Lambda API will be calling your ad-hoc container microservice, which in turn calls terraform script and passing variables to it.

https://registry.terraform.io/providers/hashicorp/aws/latest

Install code-server only by install script.

I had this problem as well since this morning and what was odd for me was that I could SSH from the terminal to the target host with no problem.

After some debugging, it seems like the Remote - SSH extension is causing the trouble. The following two options worked for me. Either:

1. Downgrading the extension to 0.70.0 works for me. The current version (0.74.0 as of now) was updated just two days ago and I think this update is causing the trouble.

2. If you would like to keep the current version, then turning off remote.ssh.useLocalServer also works. If you're on a mac, go to Code > Preferences > Settings (Cmd + ,) and then type remote.ssh.useLocalServer and it'll show the option which is turned on by default. Turning this off did the trick for me too.

My original answer didn't always work for me, so I instead decided to have my .bashrc change the shell to zsh whenever VSCode opened up a shell. You can do this by adding the following to the top of your .bashrc:

This is very much a hack and absolutely not a long term solution but as a quick work around.

Find the server.sh path in the log you posted, open it in an editor, and add --accept-server-license-terms to the last line so it looks something like "$ROOT/node" ${INSPECT:-} "$ROOT/out/server-main.js" --compatibility=1.63 --accept-server-license-terms "$@". This will accept the terms automatically until this gets patched by MS.

If you click Terminal then New Terminal, you should get a fresh terminal inside remote environment.