I used community applications to find an existing docker on docker hub. The one I chose is fbmac/mybb. I got it started using the template built by CA with almost no effort -- just mapping host port 6080 to port 80 of the container. Upon first start, I got to the setup screen and got myBB working with needo's mariaDB docker. The last set up screen said to create a blank file in /install named lock to prevent the installer from starting up again. This is where my problems started.

 

The container did not have nano installed, so I typed apt-get update, then apt-get install nano. Nano installed but would not start because TERM was not defined. After typing export TERM=xterm, nano started up and I created the lock file. I have figured out how to commit the changed container so the next time it starts up, nano will still be installed. However, the new container does not seem to save TERM=xterm so I find I have to export that again after each startup.

 

I've tried adding a variable to the template called TERM and setting it to xterm, but that does not work.  I'm sure I'm missing something simple and would appreciate some help to point me in the right direction.

If all you need is a blank file, instead of creating it with nano, why not just something similar to

cat /dev/null > whateverFileName

 

@Squid:  I can do that, but there are a ton of setting to tweak and it would be useful to be able to edit files in the container.

 

An alternative is to map the document root to a /mnt/cache/appdata/mybb. But when I did that mybb would not start saying I didn't have permission. I checked the permissions that mybb said were important and found them to be fine. I think the issue has something to do with the owner of the files on /mnt/cache/appdata/mybb is not the same as the owner of the original files in the container.

 

I used community applications to find an existing docker on docker hub. The one I chose is fbmac/mybb. I got it started using the template built by CA with almost no effort -- just mapping host port 6080 to port 80 of the container. Upon first start, I got to the setup screen and got myBB working with needo's mariaDB docker. The last set up screen said to create a blank file in /install named lock to prevent the installer from starting up again. This is where my problems started.

 

The container did not have nano installed, so I typed apt-get update, then apt-get install nano. Nano installed but would not start because TERM was not defined. After typing export TERM=xterm, nano started up and I created the lock file. I have figured out how to commit the changed container so the next time it starts up, nano will still be installed. However, the new container does not seem to save TERM=xterm so I find I have to export that again after each startup.

 

I've tried adding a variable to the template called TERM and setting it to xterm, but that does not work.  I'm sure I'm missing something simple and would appreciate some help to point me in the right direction.

 

This is how you add TERM=xterm in the dockerfile.

 

ENV TERM="xterm"