Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode server fails in Alpine:3.10 with Docker version 18.09.8 #1026

Open
aeschli opened this issue Jul 25, 2019 · 9 comments

Comments

@aeschli
Copy link

commented Jul 25, 2019

Ubuntu 18.04.2 LTS
Docker version 18.09.8

Running the remote server in alpine:3.10 (latest) crashed with a segfault.

Not sure if this is the problem, but the node that we ship with is built against alpine:3.9

@aeschli aeschli changed the title Alpine build fails in Alpine:3.10 with Docker version 18.09.8, Alpine build fails in Alpine:3.10 with Docker version 18.09.8 Jul 25, 2019

@aeschli aeschli changed the title Alpine build fails in Alpine:3.10 with Docker version 18.09.8 VSCode server fails in Alpine:3.10 with Docker version 18.09.8 Jul 25, 2019

@chrmarti chrmarti self-assigned this Aug 12, 2019

@chrmarti chrmarti added this to the August 2019 milestone Aug 12, 2019

@chrmarti

This comment has been minimized.

Copy link
Contributor

commented Aug 23, 2019

Works for me with the latest Docker (19.03.1). Could you retry with that?

@chrmarti

This comment has been minimized.

Copy link
Contributor

commented Aug 26, 2019

@aeschli Could you check if there is a newer version of image: docker pull alpine:3.10?

@chrmarti

This comment has been minimized.

Copy link
Contributor

commented Aug 27, 2019

Checked with Ubuntu 18.04 and 18.10 with the latest docker-ce, but could not reproduce.

@chrmarti chrmarti added bug upstream and removed needs-more-info labels Aug 30, 2019

@chrmarti

This comment has been minimized.

Copy link
Contributor

commented Aug 30, 2019

Most likely an upstream issue, filed https://gitlab.alpinelinux.org/alpine/aports/issues/10767.

@chrmarti

This comment has been minimized.

Copy link
Contributor

commented Aug 30, 2019

The workaround is to automatically remove spdlog from the node_modules folder when installing on Alpine 3.10. There are some follow-up errors to that module missing and there is no log file for the remote extension host. Published with 0.72.0.

@alexr00

This comment has been minimized.

Copy link
Member

commented Aug 30, 2019

Verified that I can now connect to an Alpine 3.10 container. I see the missing spdlog errors, but connection is successful.

@chrmarti chrmarti removed the candidate label Aug 30, 2019

@chrmarti chrmarti modified the milestones: August 2019, September 2019 Aug 30, 2019

@chrmarti

This comment has been minimized.

Copy link
Contributor

commented Aug 30, 2019

@Chuxel FYI, with Alpine 3.10 there will be a warning in the Dev Container terminal about this issue. Not sure if this needs to be mentioned in the documentation.

@Chuxel

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

@chrmarti Added to known issues that refers here since you get a "cannot find module" error that, while isolated to affecting our own logging, looks scary.

I'd been thinking about possibly adding an Alpine dev container into the vscode-dev-containers repo since things like setting up a non-root user are slightly different on Alpine, but I will hold off on that until we at least make the error a bit less alarming (if not get a real fix).

@chrmarti

This comment has been minimized.

Copy link
Contributor

commented Sep 6, 2019

Following-up with the musl mailing-list: https://www.openwall.com/lists/musl/2019/09/06/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.