Closed poundflag closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I have the same issue. The process in the container is using 100% of one core. There is nothing obvious that might cause this.
Same issue here. Reverting from 4.10.0 back to 4.9.1 fixed for me.
@tylrtrst How exactly do I revert to an older docker image?
@tylrtrst How exactly do I revert to an older docker image?
Change the image referenced in your docker compose file from:
lscr.io/linuxserver/code-server:latest
to:
lscr.io/linuxserver/code-server:4.9.1
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue still persists in all versions above 4.9.1.
We have not been able to reproduce this. I am currently on code-server: v4.11.0
without issues.
Getting info rather than just a blanket statement that it doesn't work would hopefully get us closer to resolving this.
Hi Rodexus,
that's valid feedback. I now upgraded to [4.11.0-ls155] and the problem is gone. It was still there in [4.11.0-ls154].
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
When trying to access the terminal the message from the screenshot appears. I am not able to use the terminal in any way (Writing in it doesn‘t work).
This is the first time I‘ve used Code-Server with docker so there may be a mistake on my part. The following screenshots show my configuration as well as the version I am using.
Expected Behavior
It should open the bash terminal, any you should be able to use it.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs