Instructions for Docker and Raspian
This commit is contained in:
parent
776f6cc408
commit
675dc31e25
43
source/_posts/docker.md
Normal file
43
source/_posts/docker.md
Normal file
@ -0,0 +1,43 @@
|
|||||||
|
---
|
||||||
|
title: Installing Docker on a Pi
|
||||||
|
date: 2018-09-02 22:43:01
|
||||||
|
thumbnail: /images/docker.png
|
||||||
|
comments: false
|
||||||
|
tags:
|
||||||
|
- Setup
|
||||||
|
categories:
|
||||||
|
- Install
|
||||||
|
- Docker
|
||||||
|
---
|
||||||
|
## Intro
|
||||||
|
Installing Docker on a Pi is super easy also.
|
||||||
|
|
||||||
|
First make sure your Raspian is up to date
|
||||||
|
```
|
||||||
|
sudo apt-get update
|
||||||
|
sudo apt-get upgrade
|
||||||
|
```
|
||||||
|
|
||||||
|
Then, all you need to do is run this.
|
||||||
|
|
||||||
|
```
|
||||||
|
curl -sSL https://get.docker.com | sudo sh
|
||||||
|
```
|
||||||
|
|
||||||
|
And voila, docker is installed:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
pi@raspian:~$ docker info
|
||||||
|
Containers: 0
|
||||||
|
Running: 0
|
||||||
|
Paused: 0
|
||||||
|
Stopped: 0
|
||||||
|
Images: 0
|
||||||
|
Server Version: 18.06.1-ce
|
||||||
|
Storage Driver: overlay2
|
||||||
|
Backing Filesystem: extfs
|
||||||
|
Supports d_type: true
|
||||||
|
Native Overlay Diff: true
|
||||||
|
```
|
||||||
|
|
||||||
|
Now, you can run [my Mystic BBS](/2018/09/01/mysticbbs/) image or [my MBSE BBS](/2018/09/04/mbse) image.
|
54
source/_posts/mbse.md
Normal file
54
source/_posts/mbse.md
Normal file
@ -0,0 +1,54 @@
|
|||||||
|
---
|
||||||
|
title: Installing MBSE BBS in Docker
|
||||||
|
date: 2018-09-04 13:07:50
|
||||||
|
thumbnail: /images/mbse.png
|
||||||
|
categories:
|
||||||
|
- Docker
|
||||||
|
- MBSE BBS
|
||||||
|
tags:
|
||||||
|
- Docker
|
||||||
|
- BBS
|
||||||
|
---
|
||||||
|
The following is the instructions on how to install [MBSE BBS](http://sourceforge.net/projects/mbsebbs) in a Docker Container. These instructions have been compiled using Docker on a Raspberry Pi. I'll provide instructions in another post on how to get Docker installed.
|
||||||
|
|
||||||
|
My image is available in my Docker Registry and can be obtained by using `docker pull registry.leenooks.net/leenooks/mbse:1.0.7.8`. You can use this image to run a container using `docker run`, or you can use it in a *swarm*, if you have multiple hosts. I actually use Docker Swarm myself.
|
||||||
|
|
||||||
|
**NOTE**: Its important that you separate "data" from the "application" and provide a persistent storage path for your container (otherwise if you recreate your container, you'll loose your data!). On my setup my container persistent storage is storage in `/srv/docker/[CONTAINER]/data`. In the parent path (/srv/docker/[CONTAINER]) I keep my scripts and tools for managing the container and starting it - and since I use Docker Swarm, that is where my `.yml` file is.
|
||||||
|
|
||||||
|
## Preparation
|
||||||
|
1. Download your favourite Linux OS and install
|
||||||
|
2. Install Docker
|
||||||
|
3. Pull the MBSE container with
|
||||||
|
|
||||||
|
```
|
||||||
|
docker pull registry.leenooks.net/leenooks/mbse:1.0.7.8
|
||||||
|
```
|
||||||
|
|
||||||
|
4. Create your persistent storage destination
|
||||||
|
|
||||||
|
```
|
||||||
|
mkdir -p /srv/docker/mbse/data
|
||||||
|
```
|
||||||
|
## Starting
|
||||||
|
5. Start your container with
|
||||||
|
|
||||||
|
```
|
||||||
|
docker run -d --rm -p 10023:23 -v /srv/docker/mbse/data:/opt/mbse/data --name=mbse leenooks/mbse:1.0.7.8
|
||||||
|
```
|
||||||
|
The first time the container starts, it will create sub directories and fill your data directory.
|
||||||
|
|
||||||
|
The options on this command line are:
|
||||||
|
|
||||||
|
<table><tr><th style="width: 20%">Option</th><th>Reason</th></tr><tr><td>-d</td><td>Run the container in the background</td></tr><tr><td>-p</td><td>Port mapping from the host:container. So using 10023:23 will mean any incoming connections on the *host* to port 10023 will be sent to the *container* on port 23. This will enable you to telnet into your MBSE.</td></tr><tr><td>-rm</td><td>Means the container will be destroyed when it is stopped. (No problem if *-v* is used below.</td></tr><tr><td>-v</td><td>Volume mapping from the host:container. A value of /srv/docker/mbse/data:/opt/mbse/data means that any data in the *container* written to /opt/mbse/data, will be stored on the *host* /srv/docker/mbse/data.</td></tr></table>
|
||||||
|
|
||||||
|
There are other options you may prefer to use, for example, instead of `--rm`, you may want to use `--restart=always`.
|
||||||
|
|
||||||
|
## Configuration
|
||||||
|
6. Now your container is running, jump into it and start configuring.
|
||||||
|
|
||||||
|
```
|
||||||
|
docker exec -itu mbse mbse /bin/bash
|
||||||
|
bin/mbsetup
|
||||||
|
```
|
||||||
|
|
||||||
|
If you need any help, [login](/2018/08/31/chinwag/) to my BBS and send me a message, or if you use another BBS, or a Sysop of a BBS and connected to one of the networks I'm connected to, you can send me a Netmail. See the list of [networks](/networks) that I'm already connected to.
|
@ -7,6 +7,7 @@ categories:
|
|||||||
- MysticBBS
|
- MysticBBS
|
||||||
tags:
|
tags:
|
||||||
- Docker
|
- Docker
|
||||||
|
- BBS
|
||||||
date: 2018-09-01 12:00:00
|
date: 2018-09-01 12:00:00
|
||||||
---
|
---
|
||||||
[Mystic BBS](http://mysticbbs.com) is great software to get up and running and get (back) into the BBS scene.
|
[Mystic BBS](http://mysticbbs.com) is great software to get up and running and get (back) into the BBS scene.
|
||||||
@ -18,7 +19,7 @@ If you would like to get up and running quickly, I've created some Docker Images
|
|||||||
There are two images:
|
There are two images:
|
||||||
<table><tr><th width="20%">Name</th><th width="80%">Information</th></tr><tr><td>armv7l</td><td>This image is a clean installation of Mystic BBS as provided by the upstream developer. It does have the pre-requisites so that spell is enabled and cryptlib is also installed so that you can use SSH based connections.</td></tr><tr><td>armv7l-extras</td><td>This image extends the base image and provides some doors and utilities.</td></tr><tr><td>x86_64</td><td>Just like the image above, however, this is for Intel Linux platforms.</td></tr><tr><td>x86_64-extras</td><td>This image extends the base image and provides some doors and utilities.</td></tr></table>
|
<table><tr><th width="20%">Name</th><th width="80%">Information</th></tr><tr><td>armv7l</td><td>This image is a clean installation of Mystic BBS as provided by the upstream developer. It does have the pre-requisites so that spell is enabled and cryptlib is also installed so that you can use SSH based connections.</td></tr><tr><td>armv7l-extras</td><td>This image extends the base image and provides some doors and utilities.</td></tr><tr><td>x86_64</td><td>Just like the image above, however, this is for Intel Linux platforms.</td></tr><tr><td>x86_64-extras</td><td>This image extends the base image and provides some doors and utilities.</td></tr></table>
|
||||||
|
|
||||||
To get the images, just install docker onto your linux platform, and then do
|
To get the images, just install docker onto your Linux platform, and then do
|
||||||
|
|
||||||
`docker pull registry.leenooks.net/leenooks/mysticbbs:1.12a39-[TAG ABOVE]`
|
`docker pull registry.leenooks.net/leenooks/mysticbbs:1.12a39-[TAG ABOVE]`
|
||||||
|
|
||||||
|
34
source/_posts/raspian.md
Normal file
34
source/_posts/raspian.md
Normal file
@ -0,0 +1,34 @@
|
|||||||
|
---
|
||||||
|
title: Installing Raspian on a Pi
|
||||||
|
date: 2018-09-01 22:26:46
|
||||||
|
thumbnail: /images/raspian.jpg
|
||||||
|
comments: false
|
||||||
|
tags:
|
||||||
|
- Setup
|
||||||
|
categories:
|
||||||
|
- Install
|
||||||
|
- Raspian
|
||||||
|
---
|
||||||
|
## Intro
|
||||||
|
Installing Raspbian on a Pi is super easy. First get hold of [Raspbian](https://www.raspberrypi.org/downloads/raspbian). I use the “Stretch-Lite” version, as it is smaller and I don't need a GUI.
|
||||||
|
|
||||||
|
You’ll need to use a tool to write the image to an SD card. If you have Linux - you can use Linux's dd command. If you use Windows or a Mac, (or you want a GUI for Linux), you can use [etcher](https://etcher.io/).
|
||||||
|
|
||||||
|
### You have two options:
|
||||||
|
|
||||||
|
1. Basic
|
||||||
|
|
||||||
|
A basic install means that you install Raspbian and it consumes the complete capacity of your SD card. This is by far the easiest and less complex setup.
|
||||||
|
|
||||||
|
The image itself as about 1.5G, and when you install it on a (larger) SD card, when Raspbian first boots, it will automatically re-partition the SD card so that the root partition consumes the remaining capacity of the SD card and reboot. On the subsequent reboot it will automatically resize that file system so that it now consumes that remaining capacity.
|
||||||
|
|
||||||
|
|
||||||
|
2. Advanced
|
||||||
|
|
||||||
|
An advanced install means that you want to control your file system layout and potentially use more mount points and/or some block devices. I went through this process because I wanted to install [glusterFS](https://www.gluster.org/) on my Pi(s) so that I can share a replicated file system with more than 1 Pi. I needed this because I wanted to use [Docker Swarm](https://docs.docker.com/engine/swarm/) (where your docker containers can float between Pis) and glusterFS provides the consistent persistent storage for those containers. And since glusterFS provides redundancy options, it means I can take a Pi offline (or in case it dies) and my BBS will start on another Pi.
|
||||||
|
|
||||||
|
To do this install, I modified the Raspbian image, so that it wouldn't resize the root file system after a reboot.
|
||||||
|
|
||||||
|
You can achieve this by removing `init=/usr/lib/raspi-config/init_resize.sh` in cmdline.txt (on the boot partition) - it should be at the end of the line.
|
||||||
|
|
||||||
|
Now you can setup [Mystic BBS](http://www.mysticbbs.com/), [MBSE BBS](http://sourceforge.net/projects/mbsebbs) or your favourite BBS software, or follow [my Docker installation](/2018/09/02/docker) if you want to run your BBS’s in docker.
|
@ -2,12 +2,30 @@
|
|||||||
title: Chinwag BBS
|
title: Chinwag BBS
|
||||||
date: 2018-08-30 21:27:43
|
date: 2018-08-30 21:27:43
|
||||||
---
|
---
|
||||||
In the early 1990's I ran a two line BBS based from St Kilda, Vic Australia called Doofus BBS. It had FidoNet node 3:632/509.
|
## About Me
|
||||||
|
|
||||||
As the Internet came around, BBS's last popularity and I grew up, got busy working, living and parenting.
|
I started BBSing in the late 80’s early 90s and run a BBS myself out of my home in St Kilda, Australia. While I only had one phone line, it was often quite busy with folks logging on mainly to exchange software. Shareware and Public Domain software was very popular and BBSes were the places to get it.
|
||||||
|
|
||||||
I recently discovered my old BBS backup disks, and wanted to see if I could bring it back online. While I haven't got there yet, I discovered a huge resurgence of BBS's and thought I'd have a play with that Software once more.
|
My computer shared the phone line with my voice callers, and if anybody wanted to ring me (voice), they had to let the phone ring twice, hang up and ring again. My BBS was programmed to ignore the second call within 10s and if I wasn't there my answering machine would get it. It was great, no telemarketing calls in those days!
|
||||||
|
|
||||||
So, today my BBS "Chinwag" is running on a Raspberry Pi in a Docker Container.
|
I did join FidoNet (3:632/509) and my friends were impressed that they could write a message, and another person anywhere in the world would reply within a few days. I also became a network hub for another network that I cannot remember now - and I recall my computer calling a Sydney BBS at 2am every morning to exchange echomail and netmail. Ahh, the phone bills just to be a sysop.
|
||||||
|
|
||||||
If you would like to take a look and be a user, you are welcome! If you need any help bringing your own BBS online, [login](/2018/08/31/chinwag/) to mine and send me a message.
|
How things have changed….
|
||||||
|
|
||||||
|
## About Chinwag
|
||||||
|
|
||||||
|
I recently discovered my BBS backups from those days and I was (and still am) keen to see if I can get it running again.
|
||||||
|
|
||||||
|
In the meantime, I did a quick google around for BBS software and BBSes in general and was amazed to see the number of people still running BBSes. Reading through the echomail recently, it is also amazing to see the number of folks coming back and setting up a BBS - some for old time sake, some to connect with friends in an environment that is not affected by hackers and SPAM.
|
||||||
|
|
||||||
|
Running a BBS is fairly easy to do these days - no need to worry about modems, fossil drivers etc, and if you get stuck a forum or email gets you help. In fact you can log into somebody else’s BBS to get help, since they are now reachable via telnet (and no phone costs). There is an abundance of software out there and many people are eager to help.
|
||||||
|
|
||||||
|
### Raspberry Pi
|
||||||
|
|
||||||
|
As such my Raspberry Pi that was sitting in my office gathering dust has been powered up and is now running Chinwag. Its probably more powerful than the computer that I had in the 90's!
|
||||||
|
|
||||||
|
I've installed Raspbian, Docker and both Mystic BBS and MBSE BBS. MBSE is my main mail hub, I like it because its written in C and operates more like a Linux BBS application. (I’m a long time Linuxer.) I also like Mystic BBS, the UI is really easy to use, it has nicer navigation and a better editor (IMHO). As I'm still re-learning the art of BBSing, I'll explore other modern legacy(!) BBS software.
|
||||||
|
|
||||||
|
The cost of a Raspberry Pi is about AUD $70 (Pi, Case and SD card) and makes a perfect BBS.
|
||||||
|
|
||||||
|
Your welcome to [login](/2018/08/31/chinwag) and have a play, and even send a message or few. And if you are interested in setting up a similar system, you can follow my posts on how to get started. First, you need to install [Raspbian](/2018/09/01/raspian).
|
||||||
|
BIN
source/images/docker.png
Normal file
BIN
source/images/docker.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 17 KiB |
BIN
source/images/mbse.png
Normal file
BIN
source/images/mbse.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 5.6 KiB |
BIN
source/images/raspian.jpg
Normal file
BIN
source/images/raspian.jpg
Normal file
Binary file not shown.
After Width: | Height: | Size: 29 KiB |
@ -13,7 +13,7 @@ customize:
|
|||||||
height: 90
|
height: 90
|
||||||
url: /images/bbs-header.png
|
url: /images/bbs-header.png
|
||||||
theme_color: '#006bde'
|
theme_color: '#006bde'
|
||||||
highlight: androidstudio
|
highlight: tomorrow-night
|
||||||
sidebar: left # sidebar position, options: left, right
|
sidebar: left # sidebar position, options: left, right
|
||||||
thumbnail: true # enable posts thumbnail, options: true, false
|
thumbnail: true # enable posts thumbnail, options: true, false
|
||||||
favicon: /images/favicon.ico # path to favicon
|
favicon: /images/favicon.ico # path to favicon
|
||||||
|
Loading…
Reference in New Issue
Block a user