Start of VSCode with devContainer creates an heavy load on the network.

[RolandJentschETAS]

Start of VSCode with devcontainer (for example SCore docs as code repo) create at startup a heavy load on the network, also if this repo was opened before.

Therefore remote work (for example in train or so) is nearly impossible, because it eats up some GByte if an hotspot from a mobile phone is used (eats up the data volume of the mobile phone).

Configuration: Windows 11 + WSL2 + VPN connection over mobile phone.

A previously opened devcontainer must not load GByte at startup.

[lurtz]

I did not experience this with Ubuntu 22.04. I suppose you did not start any command inside Visual Studio Code and it is really devcontainer startup.

Do you know if a new image was being loaded? On my system I have to actively trigger downloading new images for the latest tag and maybe this is different in your case and a new container is pulled whenever an update is available. If this is the case there is good news for you, because we have finally our first versioned image:

• https://github.com/eclipse-score/devcontainer/releases/tag/0.1.0
• https://github.com/eclipse-score/devcontainer/pkgs/container/devcontainer/572996675?tag=0.1.0

[RolandJentschETAS]

Yes, it is while startup of VSCode. I can't do anything in this moment. I can't see what going on. I have no access to the devcontainer in this moment and within WSL it is only that VSCode do something.

If I start another project (outside S-Core) within devcontainer it does not happen. Therefore something here is special.

I will recheck with the new version images.