Docker image amazon/aws-glue-libs:glue_libs_4.0.0_image_01 is not compatible with vscode 1.86 remote development

1

Microsoft Visual Studio Code recently released v1.86 which increments the required minimum version of a linux docker image to be based on at least glibc 2.28. I am doing a lot of local AWS Glue development prior to promoting the code to the AWS Glue environment and I heavily depend on AWS's Docker Container Image for AWS Glue ETL. I use glue_libs_4.0.0_image_01 which was most recently refreshed back in Nov 2023, and appears to still be built on a linux distribution with glibc 2.26, and hence vscode can no longer mount the image as a dev container. The error we get in vscode when it tries to spin up the AWS Glue dev container is:

Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib64/libstdc++.so.6.0.24
Warning: Missing GLIBC >= 2.28! from /usr/lib64/libc-2.26.so
Error: Missing required dependencies. Please refer to our FAQ https://aka.ms/vscode-remote/faq/old-linux for additional information.

For now I am forcing my vscode development environment to not upgrade, but that isn't a great long term option. I could find very minimal discussion of this issue on the web, since it is probably only a few days old, but articles like VSCode Drops Ubuntu 18.04 Support, Devs Feel “Screwed” imply that the AWS Glue docker image isn't the only one getting caught up in this.

I assume this issue will quickly show up on AWS's radar, but I don't know how widely the Glue docker images are used by people in vscode development tool chains, so I wanted to try to get this on AWS's radar sooner rather than later... and ideally get a sense of likely timeline for a newer AWS Glue docker image to be published... or some other guidance if I'm misunderstanding any of this or my options.

asked 3 months ago169 views
1 Answer
0

New to this so wondering if there is a way to know what the expectation is for "Notified the team" to turn into an update on the container? We are facing this issue as well and afraid that our corporate software update policies will force vscode update before a new container is available.

answered 3 months ago
  • TLDR: updating to vscode 1.86.1 buys us another 12 months.

    Following my post above, I found that Microsoft was discussing the impact of vscode 1.86 and it culminated in this github issue comment ( https://github.com/microsoft/vscode/issues/203375#issuecomment-1932156865) indicating that Microsoft rushed out a v1.86.1 of vscode that now just presents a warning dialog that one has to acknowledge, and I believe buys Amazon (and others) 12 months to bring their docker container images up toglibc >= 2.28. So, at least now we can continue to track with the latest vscode version and hopefully we won't be back in the same spot in 12 months.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions