-
Notifications
You must be signed in to change notification settings - Fork 5.9k
[Feature] Better CentOS support #209
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
Comments
Master had some extension loading issues. These will be resolved in the latest release. |
We'll fix up the docker container ASAP. |
@krazyito65 While you're waiting, would you be able to try RHEL 8 Beta? It's free for developers in RHD, and Coder works in that |
I need a license/account for that? The only access I have to RHEL as far as I know are the VMs that are provisioned by our corporate Unix engineering team. If I'm mistaken, please elaborate more edit: I see. Theres a 'no-cost' option for the beta. I'll see if i can get a chance to try that out. |
Is this fix in 1.32.0-245 ? Can I try to build from source to see if it fixes the extension issue? |
Ok, so I tested it a little bit more. edit: (Ignore this first part, read below) Then I tried to build from source, from this commit: (newest from when I'm typing) e3d9716 Python coloring seemed to work, but not shell (and I'm assuming here its becasue I don't have an extension for it). I also noticed that git wasn't working and showing as 'no scm prodivded' I went back to the 'release' to test some other things to see if it worked or not.... Now everything I mentioned seems to be working, but when i changed folders to my ruby workspace, If I do anything (enable or disable) to the extension the coloring goes away until a reload. So i guess on the 2nd round, the release binary seems to be working much more as expected, though needs a couple reloads to get it right.. I'll mess with it more through the week as well as getting a RHEL 8 VM going to test it there. workspaces are still wonky and don't work right, i just get a blank screen when I try to use them and i have to reload / use incognito messing with python some more, it seems i get the bug where the extension keeps sticking to be 'disabled' and i can't enable it. Although this only happens on one of my folders and not the other... I think it has something to do with the 'enable workspace' button I've been using (I've only been using it on folders and not workspaces) |
@krazyito65 do you mind sharing the centos Dockerfile you're using? |
I just used but for me, it ran everything as root, so i didn't have my usual setup |
I think I misunderstood what you originally meant by running it on centos then. I tried two approaches and failed at both.
|
I'm directly running the executable on a CentOS Machine (built using yarn from master as well as the release page) not using docker. When I used docker, I simply used what was on the main page (which I assume builds an Ubuntu image, but i haven't really looked too deep into that) |
Question. Does the new vscode extension If that uses a different code base, then I'm using that instead. |
We don't really know how VSCode's new remote features work since it's not open source. However, it's safe to say that it doesn't just run code-server on the remote machine. |
Yea, I noticed |
We already compile in CentOS7 so this is a fix IMO. Let me know if it still doesn't work. |
I just tested the latest versions; code-server2.preview.11-vsc1.37.0-linux-x86_64.tar.gz and code-server1.1156-vsc1.33.1-linux-x64.tar.gz, none of them still works, still throws:
this on centos 7.6.1810 |
Escalating this right now, I might find a fix for it. |
What a coincidence, I was trying out code-server on CentOS 7 and ran into the exact same error! |
code-server runs on my CentOS, it's the OS providing very outdated |
@elgandoz we do compile by CentOS though, the problem is we kept updating gcc (bad idea, I know) so this thing happens. |
so just to be clear; the solution provided is to first get the GCC libraries and compile them from source? and then get the code server and compile from source? |
We're gonna fix the docker build way in the CI and see if that still persist. I have a repo that makes daily builds so you can test out if that works. |
Yes but you'll need VSCode's build deps installed as well as per v2 documentation. |
Based on my investigation the
|
So please make sure your hosts have GLIBCXX 3.4.15 or higher and GLIBC 2.15 or higher. Closing this off as environment dependent and upstream dependent. Please update your CentOS hosts to be in this requirements. |
I use mostly CentOS while at work (other than my windows host machine) and I've tried to manually build and get code-server to work, which I finally did, but it seemed to be missing a lot of features.
I couldn't get extensions to stay, they would be disabled on restart and i would have to 'reinstall them' to use them. Even when I simply changed what folder I was working out of.
When messing with workspaces, I would often 'cache brick' (thats the only way I could think of describing it) where I would only get a blank screen and not be able to load the page at all. The only way I would be able to use it was through incognito. (Though I didn't try clearing my cache, but assume thats the issue since incognito worked).
From what I could see, there were 0 supported languages by default, so kind of needed an extension to do anything.
As a side, I did try the docker solution, but it would run as root which is not ideal for me since I wouldn't have access to my personal set up and any terminals i open would be root. It did seem to actually run better though since I assume it was running on an ubuntu container.
The text was updated successfully, but these errors were encountered: