Josh.5

Members
  • Posts

    498
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by Josh.5

  1. Not sure how that directory became owned by the wrong user. Have you updated file permissions on your server lately? I have pushed a small fix in the latest build that will check that directory is owned by the default user on startup before trying to start pulseaudio. This should fix the error in that log.
  2. Can you post a fresh log from `~/.cache/log/pulseaudio.err.log`. By fresh I mean, delete that file, then start the container. Then stop the container as soon as you see in the container logs that say: PULSEAUDIO: Starting pulseaudio service 2022-10-09 22:30:27,196 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-09 22:30:31,201 INFO exited: pulseaudio (exit status 1; not expected) 2022-10-09 22:30:32,203 INFO spawned: 'pulseaudio' with pid 1429
  3. How are you monitoring it exactly? And what are you monitoring it for? Is this something you could do with ssh to the host?
  4. Oh.. And sunshine and the keyboard/mouse support has been merged. There are a few little bugs with the setup tho. The initial configs need to be setup and I will need to fix a bug in NVIDIA xorg config creation (you currently need to restart the container to get inputs working). I'll be doing that in the next couple of days. I'll update the CA template again with the sunshine stuff soon also.
  5. Thought I would post this here to get any feedback. I am planning on removing the container's SSH service in the very near future. I initially added it as yet another means of accessing the container remotely for things like X forwarding, etc. But I personally never used it and I think for where the project is at, it is kind of stupid. If no one tells me in the next day or so that they are using it, I will probably rip it all out this weekend.
  6. Over the past month I have been slowly improving various aspects of Steam Headless. Here are some of the recently added updates: - Added neko as an optional alternative to noVNC (This must ne configured through environment variables). - Improved container start times. - Made all VNC and audio transport ports dynamicly configured on startup. You no longer need to specify them all to avoid conflicts, Steam Headless will find and use a random available port on startup (You can still configure them if you really want). - Added docker compose templates for other non-unraid OS. - Various bug fixes. - Updated Unraid template in CA. What I'm working on this week: - Adding sunshine to init. This will be optional to run and configured through env variables, but if enabled it will provide a really nice low latency way of accessing the desktop. - Adding keyboard and mouse pass-through support. The container already supports video out through your GPU. Now it will also support USB attached kb and mouse if you configure it to.
  7. I have noticed on lower end hardware that there are massive delays in audio sync. Even on my PC where it has poo loads of CPU to spare, the audio for noVNC is lagging by about half a second. I suspect that this is all to do with the encoding being used. There is nothing about this that is really low latency. That all being said, I would recommend leaving the VNC web UI only for tinkering and never playing games. When you want to stream the desktop with low latency, ther are better options available. I'll post an update here shortly with some if the newly added and upcoming changes to Steam Headless.
  8. I have not upgraded yet... I'll take a look when I can
  9. Yup. That prevents the host os from using the pci device.
  10. If you are saying that it is reserved, then you won't be able to access that card or use it with the host's applications
  11. I've pushed a fix for this now. Sorry it took so long.
  12. Thanks for this. I have added this to the default template. This is also a requirement to get Epic working.
  13. This is likely caused by a conflict. Are you running any other X11 servers on this PC? The log `/var/log/Xorg.55.log` (inside the container) may be useful also.
  14. You can set this in the Display settings. These should persist on restart and update of the container. Note that the NVIDIA X server settings control panel will not persist as these are stored elsewhere and are generated from scratch on startup. If you want to set the resolution from the desktop, the Display settings control panel is the one to use. If you want another way, you can also set these in the container environment variables: DISPLAY_CDEPTH="24" DISPLAY_DPI="96" DISPLAY_REFRESH="60" DISPLAY_SIZEH="900" DISPLAY_SIZEW="1600"
  15. The command that was installing the home directory template on boot was overriding these files every time. I have updated the rsync command with `--ignore-existing` so that your changes will not be over written again on boot. I also like this change that you are making so I have made it the default for new installations moving forward. Thanks
  16. That looks awesome! Have you created your own plugin repo to host this? I would like to make externally created or forked plugins more accessible to users. If you have any ideas on this, I'm all ears! If you would like this merged into the default repo also, I am happy to accept PRs from the community. I dont see these as "my plugins". These are "our plugins"
  17. There is a config option in the settings to limit the number of items in your history. Set that up and it will reduce the size of that dB file. Look for Library > Completed Tasks > Automatically manage completed tasks Set this to about 30 days and then run a library scan. It should clear out your history of items older than 30 days.
  18. You may be able to do what this is by tweaking the autostart config in the home directory. During the container startup, it creates an entry in ~/.config/autostart If you edit this file, the container startup rsync command should ignore the updated file (I think. Unless an updated container would have newer files [emoji848]). In the file, add the '-silent' flag to the Exec command line. If this file update is overwritten when the container the restarts or when you update the container, I'll need to change the rsync command used to install the home directory template during init
  19. You can run any command you like from Unmanic. The plugins that you are talking about are designed not to do that, but that is not to say a plugin could not be easily written that could.
  20. You are welcome to remain on the v0.1.4 release if that better suits your needs. Yes, Unmanic has progressed a lot since v0.1.4, however it is still free to use and not a "paid product". What you are referring to as a paid product are additional features that I have added but kept exclusive to people who support the project either by committing code on GitHub, joining in helping others on discord, or chip in financially on patreon. You do not need these additional features to use Unmanic. Take a look at these guides for getting started: https://youtube.com/channel/UCmsVRE59G_yDKk07TJF1g4A
  21. Can't remember sorry. But this is the official teamcity docker image. They will have info like that in their docs and forums
  22. Thanks for the PR. I will look into it at some point this week and get it merged. For Nginx and websockets, you need to ensure you have set "proxy_http_version 1.1;" I cant say that i have proxied this UI before, but at a guess I suspect this would work: location / { proxy_pass http://127.0.0.1:32123/; proxy_http_version 1.1; proxy_set_header Host $host:$server_port; }
  23. Yea, that looks correct. The last plugin returned false and you should then see that task failed in your completed task list