Closed adam-fowler closed 2 years ago
You're actually raising two different problems here.
The Swift LLDB failure is caused by missing capability in Docker environment. The guidance on https://hub.docker.com/_/swift?tab=tags is out of date, and you should refer to the README from this repo:
If you want to run the Swift REPL you will need to run the container with additional privileges:
# If running Docker on Linux: docker run --security-opt seccomp=unconfined -it swift # If running Docker on macOS: docker run --privileged -it swift
The CodeLLDB failure is another one: that plugin is incompatible with CentOS 7 itself, because Glibc 2.16/2.17 shipped by CentOS 7 doesn't meet its requirement of Glibc 2.18.
There's no officially prebuilt Glibc 2.18 for CentOS 7, and I think shipping a custom Glibc causes more trouble than benefits.
Going to close this as a we don't support Centos7
EDIT: Too quick there, I thought this was the vscode-swift repo, but I'll leave this closed anyway
Swift LLDB fails to launch application in 5.6-centos7 docker image.
It prints
I found this while running inside a devcontainer in Visual Studio Code. The lldb extension in VSCode returns a slightly different error message