Jump to content

Moosatronic

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by Moosatronic

  1. On 2/1/2022 at 12:52 PM, Josh.5 said:

    Glad to hear you have it working. I'll update some of the docs with your suggestions. Thanks.

    I've got an arch base build ready. It just really sucks. Because of the way that the packages work for steam and Nvidia, it requires a lot of bloat. This debian release sits at around 2GB for the docker image, the arch one pushed that closer to 3 for no reason other than the arch package repos not being a good fit for docker images.
    I also ran into some really weird input issues that I have not solved yet. Keyboard input would not work with steam in arch, but it worked in every other app or in steam big picture. I could not figure out what I was missing.
    Flatpaks are possibly a solution for running things inside the arch container, but the flatpak for steam had the same kind of issues that you have with the controller, as well as some audio issues and the fact that paths are messed up and not easily shared outside of steam.
    I'm really on the fence now as I totally wanted to keep this inline with SteamOS 3 when it was released, but now I can't see a benefit to doing so. I've put a pin in that arch docker image for the next few months until we see SteamOS 3 released.

    Yeah I tried ChimeraOS first before your docker image and it was just a mess, nevermind that ChimeraOS doesn't install a desktop which is kind of necessary to use stuff like Lutris easily. Hopefully SteamOS3 will be at least managable to port to a new container once it's released. I would assume it's just KDE + a steamos session with gamescope/steam compositor but we'll see I guess. 

    • Like 1
  2. 10 hours ago, Josh.5 said:

    Sorry, I meant "super tux"

     

    Steam creates a virtual controller when you use remote play. That's why it works in big picture but not in the game.
    https://partner.steamgames.com/doc/features/steam_controller/steam_input_gamepad_emulation_bestpractices

     

     

    1. That is fine. I think so long as it exists, then you are fine.

    2. The udev rules will not change anything here. The init scripts are setting permissions correctly (I just triple checked a clean install of the container, running a game from my phone).

    3. The input group does not exist in the container, so this would also not do anything.

     

    What may have an effect are things like:

    1. Update the permissions

    # First check the permissions
    ls -la /dev/uinput
    # Update them to rw by everyone
    chmod 666 /dev/uinput
    

    2. Try running it from another PC or device.

    So what I ended up doing was just reinstalling Steam-Headless entirely and everything now works. My mistake was, as you had suggested to someone else earlier, that I installed steam-headless before installing uinput. To save you some headaches Josh I would reccomend you make it clear in big bold letters at the top that all users should install uinput before installing steam-headless. I would think that doing so will save you and users some headaches as im sure most people will be using controllers.

     

    While I read your stuff regarding uinput, in my naevity I didn't think it was necessary for remote play controllers to work. I suspect most users will want to play using controllers so insisting on users installing uinput FIRST will likely prevent unnecessary support.

     

    also assuming once an arch-based steamos 3.0 version exists in the future, if you aren't aware of it already, I would like to suggest an additional script to install chimera, which allows you to install heroic epic games, and retroarch games directly to steam big picture mode for convenience via web on your local network. steam-headless seems like a perfect situation where chimera would be useful. dont think there's a way to install on debian but im no linux master. chimera 

  3. wasn't able to find the tux racer on steam, installed a "super tux" but the controller still didn't work.

     

    It's weird. For me, remote play with a controller works fine for big picture mode but doesn't work for most games. Interestingly however, Black Mesa was the only game workdc for me. However I think this is because the game emulates a keyboard for its "controller support". I wonder if that means that controllers work but for whatever reason they aren't assed as a controller output.

     

    some things I tried: 

     

    1. I checked "/dev/input" but only ever saw the keyboard I have plugged into my unraid server. 

     

    2. I also tried installing the steam udev rules and that didn't do anything.

     

    3. I added the user "default" to the group "input" but neither changed anything. I don't know if the docker already does this but i did it to see if anything changed but it didn't

     

    Finally one really weird thing: Josh.5, I tried your suggestion of stopping streaming and then starting it again and discovered that my controller via remote play will work for like 1 second and then will stop working. 

  4. okay i think i found the problem. I started using a different browser qutebrowser around a week or two ago which for some reason fails to show the individualized settings for each docker. Whether its due to the ad blocker or some problem with the browser myself, I have no idea. All this, and it was just the browser. 

  5. then there's the config files for my server before reset. while the files include the settings I set when dockerman worked, the settings don't appear when I go to edit them.

     

     

    Container version="2">
    <Name>qbittorrent</Name>
    <Repository>linuxserver/qbittorrent:version-14.2.5.99202004250119-7015-2c65b79ubuntu18.04.1</Repository>
    <Registry>https://hub.docker.com/r/linuxserver/qbittorrent/</Registry>
    <Network>bridge</Network>
    <MyIP/>
    <Shell>sh</Shell>
    <Privileged>false</Privileged>
    <Support>https://forums.unraid.net/topic/59191-support-linuxserverio-qbittorrent/</Support>
    <Project>https://www.qbittorrent.org</Project>
    <Overview>The qBittorrent project aims to provide an open-source software alternative to µTorrent. qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.</Overview>
    <Category>Downloaders:</Category>
    <WebUI>http://[IP]:[PORT:8080]/</WebUI>
    <TemplateURL>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/qbittorrent.xml</TemplateURL>
    <Icon>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/qbittorrent-icon.png</Icon>
    <ExtraParams/>
    <PostArgs/>
    <CPUset/>
    <DateInstalled>1603818543</DateInstalled>
    <DonateText>Donations</DonateText>
    <DonateLink>https://www.linuxserver.io/donate</DonateLink>
    <Description>The qBittorrent project aims to provide an open-source software alternative to µTorrent. qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.</Description>
    <Networking>
    <Mode>bridge</Mode>
    <Publish>
    <Port>
    <HostPort>6881</HostPort>
    <ContainerPort>6881</ContainerPort>
    <Protocol>tcp</Protocol>
    </Port>
    <Port>
    <HostPort>6881</HostPort>
    <ContainerPort>6881</ContainerPort>
    <Protocol>udp</Protocol>
    </Port>
    <Port>
    <HostPort>8080</HostPort>
    <ContainerPort>8080</ContainerPort>
    <Protocol>tcp</Protocol>
    </Port>
    </Publish>
    </Networking>
    <Data>
    <Volume>
    <HostDir>/mnt/user/Media/</HostDir>
    <ContainerDir>/downloads</ContainerDir>
    <Mode>rw</Mode>
    </Volume>
    <Volume>
    <HostDir>/mnt/user/appdata/qbittorrent</HostDir>
    <ContainerDir>/config</ContainerDir>
    <Mode>rw</Mode>
    </Volume>
    </Data>
    <Environment>
    <Variable>
    <Value>99</Value>
    <Name>PUID</Name>
    <Mode/>
    </Variable>
    <Variable>
    <Value>100</Value>
    <Name>PGID</Name>
    <Mode/>
    </Variable>
    </Environment>
    <Labels/>
    <Config Name="Host Port 1" Target="6881" Default="6881" Mode="tcp" Description="Container Port: 6881" Type="Port" Display="always" Required="true" Mask="false">6881</Config>
    <Config Name="Host Port 2" Target="6881" Default="6881" Mode="udp" Description="Container Port: 6881" Type="Port" Display="always" Required="true" Mask="false">6881</Config>
    <Config Name="Host Port 3" Target="8080" Default="8080" Mode="tcp" Description="Container Port: 8080" Type="Port" Display="always" Required="true" Mask="false">8080</Config>
    <Config Name="Host Path 2" Target="/downloads" Default="" Mode="rw" Description="Container Path: /downloads" Type="Path" Display="always" Required="true" Mask="false">/mnt/user/Media/</Config>
    <Config Name="Key 1" Target="PUID" Default="99" Mode="" Description="Container Variable: PUID" Type="Variable" Display="always" Required="false" Mask="false">99</Config>
    <Config Name="Key 2" Target="PGID" Default="100" Mode="" Description="Container Variable: PGID" Type="Variable" Display="always" Required="false" Mask="false">100</Config>
    <Config Name="AppData Config Path" Target="/config" Default="/mnt/user/appdata/qbittorrent" Mode="rw" Description="Container Path: /config" Type="Path" Display="advanced-hide" Required="true" Mask="false">/mnt/user/appdata/qbittorrent</Config>
    </Container>

     

  6. the template is as follows:

     

    Container version="2">
    <Name>qbittorrent</Name>
    <Repository>linuxserver/qbittorrent:version-14.2.5.99202004250119-7015-2c65b79ubuntu18.04.1</Repository>
    <Registry>https://hub.docker.com/r/linuxserver/qbittorrent/</Registry>
    <Network>bridge</Network>
    <MyIP/>
    <Shell>sh</Shell>
    <Privileged>false</Privileged>
    <Support>https://forums.unraid.net/topic/59191-support-linuxserverio-qbittorrent/</Support>
    <Project>https://www.qbittorrent.org</Project>
    <Overview>The qBittorrent project aims to provide an open-source software alternative to µTorrent. qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.</Overview>
    <Category>Downloaders:</Category>
    <WebUI>http://[IP]:[PORT:8080]/</WebUI>
    <TemplateURL>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/qbittorrent.xml</TemplateURL>
    <Icon>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/qbittorrent-icon.png</Icon>
    <ExtraParams/>
    <PostArgs/>
    <CPUset/>
    <DateInstalled>1603818543</DateInstalled>
    <DonateText>Donations</DonateText>
    <DonateLink>https://www.linuxserver.io/donate</DonateLink>
    <Description>The qBittorrent project aims to provide an open-source software alternative to µTorrent. qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.</Description>
    <Networking>
    <Mode>bridge</Mode>
    <Publish>
    <Port>
    <HostPort>6881</HostPort>
    <ContainerPort>6881</ContainerPort>
    <Protocol>tcp</Protocol>
    </Port>
    <Port>
    <HostPort>6881</HostPort>
    <ContainerPort>6881</ContainerPort>
    <Protocol>udp</Protocol>
    </Port>
    <Port>
    <HostPort>8080</HostPort>
    <ContainerPort>8080</ContainerPort>
    <Protocol>tcp</Protocol>
    </Port>
    </Publish>
    </Networking>
    <Data>
    <Volume>
    <HostDir>/mnt/user/Media/</HostDir>
    <ContainerDir>/downloads</ContainerDir>
    <Mode>rw</Mode>
    </Volume>
    <Volume>
    <HostDir>/mnt/user/appdata/qbittorrent</HostDir>
    <ContainerDir>/config</ContainerDir>
    <Mode>rw</Mode>
    </Volume>
    </Data>
    <Environment>
    <Variable>
    <Value>99</Value>
    <Name>PUID</Name>
    <Mode/>
    </Variable>
    <Variable>
    <Value>100</Value>
    <Name>PGID</Name>
    <Mode/>
    </Variable>
    </Environment>
    <Labels/>
    <Config Name="Host Port 1" Target="6881" Default="6881" Mode="tcp" Description="Container Port: 6881" Type="Port" Display="always" Required="true" Mask="false">6881</Config>
    <Config Name="Host Port 2" Target="6881" Default="6881" Mode="udp" Description="Container Port: 6881" Type="Port" Display="always" Required="true" Mask="false">6881</Config>
    <Config Name="Host Port 3" Target="8080" Default="8080" Mode="tcp" Description="Container Port: 8080" Type="Port" Display="always" Required="true" Mask="false">8080</Config>
    <Config Name="Host Path 2" Target="/downloads" Default="" Mode="rw" Description="Container Path: /downloads" Type="Path" Display="always" Required="true" Mask="false">/mnt/user/Media/</Config>
    <Config Name="Key 1" Target="PUID" Default="99" Mode="" Description="Container Variable: PUID" Type="Variable" Display="always" Required="false" Mask="false">99</Config>
    <Config Name="Key 2" Target="PGID" Default="100" Mode="" Description="Container Variable: PGID" Type="Variable" Display="always" Required="false" Mask="false">100</Config>
    <Config Name="AppData Config Path" Target="/config" Default="/mnt/user/appdata/qbittorrent" Mode="rw" Description="Container Path: /config" Type="Path" Display="advanced-hide" Required="true" Mask="false">/mnt/user/appdata/qbittorrent</Config>
    </Container>

     

  7. I made a previous post regarding this issue but I wanted to start a new one as the problem is slightly different from how I first stated it.

     

    all docker templates do not work and I am given no settings particular to a template both from docker containers I had already installed and new containers from the community repository. Here's a picture to give you an idea, all of my docker containers are like this, clicking advanced doesn't reveal any individualized settings in a template https://i.imgur.com/ldrwaOH.png . Even trying to install new containers I get this exact same lack of settings.

     

    Things i've tried:

    1. I turned on and off template authoring mode in the unraid docker settings.
    2. I created a fresh install of unraid on a new flash drive. reinstalled community plugins, etc.
    3. I created a new share and set the docker engine to use that share.
    4. I removed all of my docker containers and started anew.
    5. deleted my docker.img file

     

    Nothing has worked, so I thought I would ask here for help. I've also included a diagnostics zip as an attachment.

     

     

    tower-diagnostics-20210220-1725.zip

  8. Hello this is a general issue from a relative docker newbie. 

     

    I've been using docker on unraid for a few months now but have run into the issue of the individual settings for each docker disappearing. As you likely know normally each docker at least with dockerman in unraid gives you some settings to change for that specific docker. After a reboot I was surprised to see these settings have disappeared from all of my containers. Installing new docker containers doesn't change anything as no options appear when installing or reinstalling containers. Is there anything I can do? also clicking for "advanced" options doesn't seem to solve it as one person on reddit suggested.

    docker problem.png

×
×
  • Create New...