NIronwolf

I had been using multitail inside a tmux recently and everything was working great. About a week ago or so I wandered by the Nerd Pack page and let everything update. Now when I try to run multitail inside of tmux it only gives the following error. Error opening terminal: tmux-256color. I'm not much of a linux expert. Barely a user. Is there something that I'm doing wrong? These are the packages I have NP loading: ctop-0.7.3-x86_64-1.txz iotop-0.6-x86_64-1_fs.tgz mediainfo-19.09-x86_64-1_SBo.txz multitail-6.4.2-x86_64-1.txz ncurses-terminfo-6.1.20191130-x86_64-1.txz perl-5.32.0-x86_64-1.txz python-2.7.11-x86_64-2.txz tmux-3.1.0-x86_64-1.txz Logging in with Putty 0.67 from Windows 10. Thanks!

Did you ever find an answer to this?

I discussed with the crafty devs in their Discord. They plan to update the thread management in v4. As of right now, the only work around I've found is restarting the container.

This solution works perfectly for running multiple instances of Factorio on unRAID. Thank you.

Sorry to revive this, and it may rest with the docker container author, but to shed a bit of light on it, it seems the container hard codes the startup command for the game to have a --port 34197 parameter. So when you run a second instance, when it communicates to the Wube matching server it reports this port (despite asking docker to map it to another port and it comes in/out of your firewall/network at this other port) so when you try to connect to the second instance, it tells the remote client to connect on this hard coded command line port parameter and hits the original server. Is this in your wheelhouse to edit or do I need to contact the container maintainer? The port to use is not set in the configuration files, it's set from that command line. Sorry I'm still newish to unRAID/Docker so I don't know if just an environment variable can be added or something.