Hi everyone,

 

I'm trying to solve an issue with a particular docker app after making some hardware changes that also affected networking. Essentially, paperless ngx won't start properly because apparently it can't connect to the redis database running in a different docker container.

 

In the log I've found that the IP address where the database is looked up is wrong, that is to say: it's an IP adress that was once assigned to the unraid server but isn't anymore.

 

Redis ping #2 failed.
Error: Error 113 connecting to 192.168.old.ip:6379. No route to host..
Failed to connect to redis using environment variable PAPERLESS_REDIS.

 

The container won't start up properly so I can't change the setting in its own interface. I've searched the appdata folder for a configuration file but didn't find any. In order to solve the issue, it appears that I need to change a setting stored in some variable.

 

The problem is that I really don't know how this is done.

 

It seems that my fundamental problem is that I don't understand how Docker works (as opposed to, say, a VM). Generally speaking, where do I make configuration changes? And specifically to my issue, where do I set this environment variable?

 

 

Docker Tab, click the icon and select "Edit". There you can modify any variables you set originally or change them etc.

I seem to recall doing that kind of thing in the past, but for whatever reason I can't seem to find the "edit" option.

 

 

Man, and another post where no solution was given. I have this same issue from trying to add --hostname to the extra run but had cut off the host part, so the container rename itself mid-creation and that messed up everything. It's upsetting there's no obvious way to edit a docker container or to at least do it manually

Because "edit" is based upon the name matching the template.  If the template doesn't exist, the implication is that you either created the container yourself at the command line and are managing it yourself, or by another application and that application is managing the container.  Your situation is closest to the first.

 

Not really sure how to handle the inadvertent change that you had added to the command being issued...