Lenir Santiago

I'm getting the same issue... Do I have to run another docker instance for media server?

I'm trying the latest version and I'm getting this error message in the logs: 2024-08-30 16:22:27.671280 [info] Starting Supervisor... 2024-08-30 16:22:28,155 INFO Included extra file "/etc/supervisor/conf.d/code-server.conf" during parsing 2024-08-30 16:22:28,156 INFO Set uid to user 0 succeeded 2024-08-30 16:22:28,160 INFO supervisord started with pid 7 2024-08-30 16:22:29,165 INFO spawned: 'start-script' with pid 96 2024-08-30 16:22:29,166 INFO reaped unknown pid 8 (exit status 0) 2024-08-30 16:22:30,168 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-08-30 16:22:30,777 DEBG 'start-script' stdout output: [2024-08-30T20:22:30.772Z] info code-server 4.92.2 de65bfc9477f61bc22d0b1a23085d1f18bb25202 2024-08-30 16:22:30,778 DEBG 'start-script' stdout output: [2024-08-30T20:22:30.775Z] info Using user-data-dir /config/code-server/data 2024-08-30 16:22:30,790 DEBG 'start-script' stderr output: [2024-08-30T20:22:30.789Z] error EISDIR: illegal operation on a directory, read 2024-08-30 16:22:30,820 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23124701636144 for <Subprocess at 23124713605888 with name start-script in state RUNNING> (stdout)> 2024-08-30 16:22:30,821 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23124701809888 for <Subprocess at 23124713605888 with name start-script in state RUNNING> (stderr)> 2024-08-30 16:22:30,821 WARN exited: start-script (exit status 1; not expected) 2024-08-30 16:22:30,822 DEBG received SIGCHLD indicating a child quit I did verify that /config/code-server/data directory exists... I even tried calling other directories, but it's always the same error.

Hi everyone, Just a quick update for those of you who are still trying to install ChromeOS/PrimeOS. After a lot of trial and error, I was able to successfully install PrimeOS on Unraid 6.8.3. I used the ChromeOS template, using Machine type Q35-4.2, OVMF Bios and SATA for all storage. Also, the only version I was able to install was PrimeOS Classic v0.4.5. NOTE: I wasn't able to get the the Mainline and Standard ISOs to work, only the Classic version. Also, to install PrimeOS, I had to use the Advanced->AutoUpdate option in Grub once the VM boots from the ISO. Once you install PrimeOS, in order to get PrimeOS to use Ethernet instead of Wifi, go to Settings->PrimeOS Settings and enable "Show connection type WiFi to apps" Enjoy!