Once you have everything edited, you can click the “Deploy the Container” button and wait a couple of minutes for it to deploy. The third and fourth lines are optional as they are just mount points if you have additional hard drive locations that you want to mount and have access to in Krusader. You can leave the second line alone as it is just for setting the time zone of your application. The first line is where your configuration files will go, so edit the first half of that line. Once you copy that into your Portainer Stack, you’ll want to modify the volumes a bit. NOTE: This is running with elevated privileges and as root, so be careful with this. srv/dev-disk-by-label-Files/Config:/mnt/myconffiles #replace the first half of this with where *your* files / extra drives are located srv/dev-disk-by-label-Files:/mnt/myfiles #replace the first half of this with where *your* files / extra drives are located srv/dev-disk-by-label-Files/Config/MyKrusader:/config I want to run it in a Portainer Stack, so I rewrote what benhex had into a stack:. The issue that I ran into is that the benhex page only had a Docker command that would be run in an SSH screen. When doing research for this, I ran into a few different versions of Krusader, but found the one from binhex to be the easiest to setup. Krusader is an advanced twin panel (commander style) file manager for KDE Plasma and other desktops in the *nix world, similar to Midnight or Total Commander.