Subj : Re: Docker BBS Setup To : Black Panther From : alterego Date : Mon Sep 28 2020 08:45:54 Re: Re: Docker BBS Setup By: Black Panther to alterego on Sun Sep 27 2020 02:29 pm Howdy, BP> I thought you might have been ignoring me, but it looks like the BP> connection between here and tqwNet wasn't working for a couple days. :) Yeah, thats the only bummer with Fido - is that you dont know if your messages got received by the other end, and sometimes you wait for a reply that will never come... Would love to fix that somehow ... BP> Just to verify, a docker image is not dependent on the systems os. The BP> reason I'm asking, is I'll be working on getting this running on Manjaro, BP> but will probably set up the hub system to run Debian. If I remember BP> correctly, that will not be an issue, but wanted to double check. Right. I move containers all the time between my MAC, CentOS and Debian. One of the values is that it doesnt matter what the host is running, because the container has everything it needs inside it to run. I've only ever had 1 strange problem, moving an Intel container from an Intel PC to a APU1D (running an AMD processor) - and the app kept segfaulting with SIGILL. In that case I had to rebuild (which resulted in recompiling the app) and then it ran fine. So, another benefit of Docker, if you do rebuild - the "recipe" to rebuild is in the "Dockerfile" - so very little needs to change (if any) - the build command is "docker build". I do this all the time as well, testing my "building" on an Intel (because its super fast - and sometimes on my MAC), and then once the container build fine (expecially if it involves compiling something), I then build it on the Pi (which is sloooower!). As an example, my Synchronet takes about 5mins (full build) on the Intel and over an hour on the Pi - and its the same Dockerfile (minus dosemu items). BP> So all of these paths will be persistent, and outside of the container? al>> SRC=/srv/docker/fidohub Yes, so if $SRC is a real directory on the host (can be /mnt/a on machine 1, and /mnt/b on machine 2), inside the container: al>> -v ${SRC}/binkd:/etc/binkd \ /etc/binkd still has binkd's config and the container doesnt know that a) its a container, and b) where the files are stored on the host. BTW: Leave those dirs empty in the start, and the container will pre-populate them with a default config (that does need to be tweaked) - but enough to get you started. If you want to chat live with help, find me on matrix, you can sign up to my matrix.leenooks.net server, or use matrix.org. I'm @deon:matrix.leenooks.net You can use a matrix client (I use element), or https://app.element.io ....лоеп .... Anyone can get old. All you have to do is live long enough. --- SBBSecho 3.11-Linux * Origin: I'm playing with ANSI+videotex - wanna play too? (1337:2/101) .