Jump to content

Docker Error


minuzle

Recommended Posts

I've recently moved all my drives into a server case.  I noticed that I'm getting an error on the Docker page under "Docker Images"

 

Fatal error: Call to a member function getDockerImages() on null in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(300) : eval()'d code on line 6

 

I've tried to search for an answer but I haven't had any luck.

 

Any ideas?

 

Thanks

 

minuzle

Link to comment

I've recently moved all my drives into a server case.  I noticed that I'm getting an error on the Docker page under "Docker Images"

 

Fatal error: Call to a member function getDockerImages() on null in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(300) : eval()'d code on line 6

 

I've tried to search for an answer but I haven't had any luck.

 

Any ideas?

 

Thanks

 

minuzle

What version of unRaid?
Link to comment

This is what it says now:

 

Fatal error: Uncaught Error: Call to a member function getDockerImages() on null in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(376) : eval()'d code:6 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(376): eval() #1 /usr/local/emhttp/plugins/dynamix/template.php(61): require_once('/usr/local/emht...') #2 /usr/local/src/wrap_get.php(16): include('/usr/local/emht...') #3 {main} thrown in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(376) : eval()'d code on line 6

 

I've included the diagnostics if that will help

 

Thanks

 

 

minuzle

mediasrv-diagnostics-20170204-1354.zip

Link to comment

Are you seeing these errors on the same browser window that you reset the system on?  You've also got a bunch of wrong csrf_token errors which are generally caused by another browser window and/or another device attempting to access the server that was fired up before the reboot, but is still active.

 

IE: Close any and all browser windows on all devices that are pointed to unRaid and try again.

 

Beyond that, I really don't know what's going on with your error messages.  Best guess is to nuke the docker.img file and start over again by installing the my* templates or via CA's Previous Apps section.  All appdata etc will still be there either method and all the templates will be already filled out properly

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...