Jump to content

CryoRig

Members
  • Posts

    37
  • Joined

  • Last visited

Posts posted by CryoRig

  1. So you want to integrate both into CA? Is this your plan or unraids?

     

    Sorry if this sounds mean but what the hell? Why would i choose the extremly space inefficient ca style over the current list style? 

    That makes no sense to me... 

    I guess if this is happening i should look for a different managment for my containers

     

    Edit

    Please don't take this wrong. 

    I am not saying ca looks bad, just that the catalog style that works great for ca doesn't work for managment of a whole range of containers/plugin lists. At least in my opinion. 

    • Upvote 2
  2. As its "just" an annoyance not a problem, i understand that you probably don't want to invest much time into adding an option to disable it...

    As to why

    I don't really see the usecase for myself. 

    It shows that i have container or plugins which need updates

    That functionality is already there. Plugin/docker page.

    In my case i have some container that i can't update for compatibility resons, which means it is always there blinking like something is wrong... 

    It also feels like its taking longer to load, probably just placebo but again "just" annoying.

    I hope that explains the why :)

  3. 5 minutes ago, ich777 said:

    Can you change the path from /mnt/user/... to /mnt/cache/... in the template, then it should work, allready updated the template (but this will take some time that it updates) and also updated the container itself there was another issue (maprotationfile was not properly downloaded).

    That worked, weird bug though
    thanks

    • Like 1
  4. all the pak[0-8].pk3 are there

    -rwxrwx--- 1 nobody users 479493658 Mar 21 18:53 pak0.pk3*
    -rwxrwx--- 1 nobody users    374405 Mar 21 18:53 pak1.pk3*
    -rwxrwx--- 1 nobody users   7511182 Mar 21 18:53 pak2.pk3*
    -rwxrwx--- 1 nobody users    276305 Mar 21 18:53 pak3.pk3*
    -rwxrwx--- 1 nobody users   9600350 Mar 21 18:53 pak4.pk3*
    -rwxrwx--- 1 nobody users    191872 Mar 21 18:53 pak5.pk3*
    -rwxrwx--- 1 nobody users   7346884 Mar 21 18:53 pak6.pk3*
    -rwxrwx--- 1 nobody users    320873 Mar 21 18:53 pak7.pk3*
    -rwxrwx--- 1 nobody users    454478 Mar 21 18:53 pak8.pk3*

  5.  Quake 3 Fails to start
    after i added the pak0.pk3 file, the server stopps with this error:

     

    ----- FS_Startup -----
    Current search path:
    /quake3/.q3a/demota
    /quake3/demota
    /quake3/q3ded/demota
    
    ----------------------
    0 files in pk3 files
    Sys_Error: Couldn't load default.cfg
    ---Checking if UID: 99 matches user---
    usermod: no changes
    ---Checking if GID: 100 matches user---
    usermod: no changes
    ---Setting umask to 000---
    ---Checking for optional scripts---
    ---No optional script found, continuing---
    ---Checking if Quake3 is installed---
    ---Quake 3 found, continuing...---
    ---Starting...---
    ---Checking if .pk3 files are present---
    ---pak0.pk3 found, continuing---
    ---Prepare Server---
    ---Checking if 'server.cfg' is present---
    ---'server.cfg' found, continuing---
    ---Checking if 'maprotation.cfg' is present---
    ---'maprotation.cfg' found, continuing---
    ---Server ready---
    ---Starting server---
    Q3 1.32c linux-i386 May  8 2006
    ----- FS_Startup -----
    Current search path:
    /quake3/.q3a/baseq3
    /quake3/baseq3
    /quake3/q3ded/baseq3
    
    ----------------------
    0 files in pk3 files
    
    Running in restricted demo mode.
    
    ----- FS_Startup -----
    Current search path:
    /quake3/.q3a/demota
    /quake3/demota
    /quake3/q3ded/demota
    
    ----------------------
    0 files in pk3 files
    Sys_Error: Couldn't load default.cfg

     

×
×
  • Create New...