deploy-code-server VS docker-mods

Using our one-click buttons and guides to deploy code-server to a cloud provider ⚡

There's also a bunch of guides for deploying code-server to different services here: https://github.com/coder/deploy-code-server

I recently heard about an open source project called code-server, which is maintained by the people behind Coder, and lets you access a remote VS Code process from the browser. Deploying code-server to Render feels like a good place to start my exploration. I'm excited to discover an additional repo that helps with deploying code-server to cloud hosting platforms. The repo includes a Dockerfile, so I suspect we can deploy it to Render without any changes.

The answer is yes and there are a lot of different solutions for it: 1. Use Gitpod.io (supported Github, Gitlab, Bitbucket,...) 2. Use Github CodeSpaces (Only Github, ofc) 3. Host your own code-server (https://github.com/cdr/deploy-code-server)

Have you tried adding the OpenCL-Intel Dockermod for the LSIO container? I don't believe it'll function properly without it...fair warning it significantly increases startup time. Additionally, it may not matter if you've already verified your hardware acceleration is working as expected, but at one point I did have to specifically indicate both renderD128 and card0 to get everything settled. If it ain't broke, don't fix it, but that's a difference in our compose files I spotted immediately.

Misc - LinuxServer.io images now support mods with multi-digest layers (https://github.com/linuxserver/docker-mods/pull/577)

Are you using a linuxserver container? If so, check this out as well: https://github.com/linuxserver/docker-mods/tree/jellyfin-opencl-intel

If you are running using the lsio container, you could try out this repo which makes the par2 process 2-3 times faster. https://github.com/linuxserver/docker-mods/tree/sabnzbd-par2cmdline-turbo

If you're using the LinuxServer plex image, you're probably facing this issue. https://github.com/linuxserver/docker-mods/issues/575

Following this issue and looking at the code here it appears that the mod identifies running applications on swag by globbing all the conf files (including samples!) and attemting a connection on them. And it does this with ThreadPoolExecutor(max_workers=100) which seems to explain why those DNS queries were being spammed on pihole.

I run a similar set up, but i run jellyfin with linuxserver's docker with this addon: https://github.com/linuxserver/docker-mods/tree/jellyfin-amd