add dev container for clone issue

[Vediusse]

mac os dont have sys call "clone", so mac users can use dev container in vccode

[Vediusse]

@vityaman

[vityaman]

Need only lldb, clang and cmake extensions. There is some fresh cool CMake extension with an LSP.

[e1turin]

+ clangd

[vityaman]

Let's use Clang.

[vityaman]

@e1turin, what do you think about it?

[vityaman]

I have some concerns that this image is not used in workflows and and therefore is not tested.

[e1turin]

why it is in separate layer?

[e1turin]

+ clangd

[e1turin]

What's the reason of docker-compose? Why not to use simple Dockerfile?

[e1turin]

I have some concerns that this image is not used in workflows and and therefore is not tested.

Yes, I think some tests should be provided. And instead of setting up lot's of dependencies manally, it whould be better to use prepared image (from current CI) with clang.

[Vediusse]

i have a solve w/o docker-compose, FROM ubuntu and gcc, but there are problems with setting up the code lldb extension for debugging. It always returns the error "spawn cargo ENOENT" or "lldb-mi not found" when pressed debug button. Do you have some json configs or smth like that, to solve this issues ?

[Vediusse]

And what test are you talking about ? @e1turin @vityaman

[e1turin]

How you can proof that your configuration works?

[e1turin]

i have a solve w/o docker-compose, FROM ubuntu and gcc, but there are problems with setting up the code lldb extension for debugging. It always returns the error "spawn cargo ENOENT" or "lldb-mi not found" when pressed debug button. Do you have some json configs or smth like that, to solve this issues ?

No I have never faced the problem. I think you can find complete devcontainer setup for macos which may help.

[Vediusse]

How you can proof that your configuration works?

I consider this configuration to be very minimal—basically only for running and debugging. Therefore, I thought writing additional tests is unnecessary. I can confirm, however, that I’ve already completed the first lab and the CI test results matched those in the dev container.

[Vediusse]

No I have never faced the problem. I think you can find complete devcontainer setup for macos which may help.

I was only able to make a little progress on solving this task. LLDB now launches, but there’s an issue with the external terminal—currently the terminal just idle and nothing happens. Can I hook up the old debug tool instead? If someone specifically needs LLDB, that person can set up the launch.json and Docker configuration correctly. Cause I ve done lab1 w\o lldb and cant remember problems with it

[Vediusse]

@vityaman @e1turin

I solved the issue with lldb and the inability to debug. The issue was described here:

https://forums.docker.com/t/sys-ptrace-capability-for-linux-amd64/138482

Exactly the same error description. I couldn't find a solution; it's likely due to an incompatibility between m1 processors and Debian-based Docker. If I change FROM silkeh/clang:latest to FROM ubuntu:24.04 in Docker, everything works. What do you think about using a non-CI/CD image but still providing users with debugging capabilities? I haven't had any issues with Ubuntu during my work.