I figured we could bring this conversation into a Docker related area. :)
So, if I'm looking at changing a Windoze computer over to Linux, it wouldprobably be a good idea to create a docker image in a Linux
container, and get that set up, have that run on a different computer,then change the OS on the physical computer, and continue to
run the docker image on the new setup.
Let me start with, how do I start setting up the creation of my own image?
have it copy into the image? Or, does it need to be set up within theimage?
So, if you are wanting to run hpt/binkd in a docker image, I would startby pulling my image and playing with it. If you find it is
missing things, or you want things added to the image, you can then extend
So I thought I'd provide some steps and we can go from there:
1. Install Docker
2. Pull my image to play with:
docker pull registry.leenooks.net/bbs/fidohub:latest-x86_64 (or armv7l
if you doing a Pi).
SRC=/srv/docker/fidohub
-v ${SRC}/binkd:/etc/binkd \
-v ${SRC}/ftn:/etc/ftn \
-v ${SRC}/fido:/fido \
-v ${SRC}/tools:/usr/local/tools \
-v ${SRC}/log:/var/log/fido \
This is apt, I've just spent a few days this week moving over my systems to Docker too.
I came across a few of Deons images and they were very useful.
I thought you might have been ignoring me, but it looks like the connection between here and tqwNet wasn't working for a couple days. :)
Just to verify, a docker image is not dependent on the systems os. The reason I'm asking, is I'll be working on getting this running on Manjaro, but will probably set up the hub system to run Debian. If I remember correctly, that will not be an issue, but wanted to double check.
So all of these paths will be persistent, and outside of the container?
SRC=/srv/docker/fidohub
-v ${SRC}/binkd:/etc/binkd \
Keep this discussion going guys, I am very interested in Docker Images
for a project I am doing with a Commodore Emulator...
Keep this discussion going guys, I am very interested in Docker Images for
I haven't done anything yet with actual images in docker. I've done thetutorials, like hello-world, web server, etc... For some
reason, this is
taking a bit to wrap my head around...
1. Install Docker
That's fairly easy, and with a Linux distro installed (I use CentOS, Debian), you can do:
2. Pull my image to play with:
docker pull registry.leenooks.net/bbs/fidohub:latest-x86_64 (or armv7l
if you doing a Pi).
I have DOSEMU running in a container, running my 1995 BBS with Portal of Power :)
2. Pull my image to play with:
docker pull registry.leenooks.net/bbs/fidohub:latest-x86_64 (or
armv7l if you doing a Pi).
Had an error on this one:
docker pull registry.leenooks.net/fidohub:latest-x86_64
Error response from daemon: Get https://registry.leenooks.net/v2/fidohub/manifests/latest-x86_64:
denied: access forbidden
you would need to do is forward the fqtn to the correct ip address.. We are about to release the update to Image BBS v3.0 and I am doing the same thing with the BBS On a Stick, except this time I want to do something like it in Linux. So a Container might be the way to go. I could completely set up everything and the SysOp would only have to pull up the container and set his IP address again.. We'll see how it goes..
Had an error on this one:
docker pull registry.leenooks.net/fidohub:latest-x86_64
docker pull registry.leenooks.net/fidohub:latest-x86_64
Wow, this triped me up as well.
The URL is registry.leenooks.net/bbs/fidohub:latest-x86_64
(You missed the /bbs/ in the URL :)
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.
Boy do they need to be tweaked... :) Luckily, I still had the fidoconfigand binkd.cfg from Hub 4. I just need to go through and change all of the paths, and create directories. That's gonna take me a bit. :)
On 27 Sep 2020, alterego said the following...
1. Install Docker
That's fairly easy, and with a Linux distro installed (I use CentOS, Debian), you can do:
That's already installed.
2. Pull my image to play with:
docker pull registry.leenooks.net/bbs/fidohub:latest-x86_64 (or armv7 if you doing a Pi).
Had an error on this one:
docker pull registry.leenooks.net/fidohub:latest-x86_64
Error response from daemon: Get https://registry.leenooks.net/v2/fidohub/manifests/latest-x86_64:
denied: access forbidden
On 28 Sep 2020, Black Panther said the following...
On 27 Sep 2020, alterego said the following...
1. Install Docker
That's fairly easy, and with a Linux distro installed (I use Cen Debian), you can do:
That's already installed.
2. Pull my image to play with:
docker pull registry.leenooks.net/bbs/fidohub:latest-x86_64 (or if you doing a Pi).
Had an error on this one:
docker pull registry.leenooks.net/fidohub:latest-x86_64
Error response from daemon: Get https://registry.leenooks.net/v2/fidohub/manifests/latest-x86_64: denied: access forbidden
Dan,
I think you missed the `/bbs/` part of the url off...
you said you did:
docker pull registry.leenooks.net/fidohub:latest-x86_64
deon said to do:
docker pull registry.leenooks.net/bbs/fidohub:latest-x86_64
^^^
See if that works?
It should be completely doable. If you can get Ezycom running in a docker container (which is what I have) with Portal of Power, this should be a sinch as well.
Yell out if you get stuck, I'm happy to help where I can..
I think you missed the `/bbs/` part of the url off...
Sorry, I replied to that in the order I read the messages, and literally the next message or so after I see you discovered your typo so ignore
this lol.
Sysop: | Saxainden |
---|---|
Location: | Littleton, CO |
Users: | 30 |
Nodes: | 10 (0 / 10) |
Uptime: | 05:25:09 |
Calls: | 350 |
Messages: | 36,664 |