OpenSimuator Configuration Sandbox

Some example OpenSimulator configuration setups, using Docker (should also be compatible with Podman) for quick prototyping.

For accessing the OpenSimulator metaverse, I recommend Firestorm Viewer.

Experiments

Each folder contains a docker-compose file that will setup the OpenSimulator prototype.

Folder	Purpose
standalone	Sets up an OpenSimulator instance in standalone mode, using MySQL (mariadb 10.5) as the storage engine.
standalone-wordpress	Same as Standalone, but has a WordPress instance prepped to control the userbase.
standalone-hypergrid	Same as Standalone, with Hypergrid capabilities that can connect to other servers.

Using Docker Compose / Cheat Sheet

• Start up an experiment: docker-compose up --build -d
  • --build will build the Docker file needed for OpenSimulator.
  • -d is optional - it brings you back to a prompt. If omitted, your terminal is locked to output (can return by typing docker-compose logs).
• Stop experiment: docker-compose stop
• Destroying: docker-compose down -v
  • -v will remove the associated volumes (e.g. database storage data). If you keep it, the files will still hang around for the next up.

Troubleshooting

I'm not able to run commands in the OpenSimulator prompt

You are able to attach a shell to the current entrypoint, but so far this doesn't seem to work for me. You can 'cheese' this process by adding screen, allowing you to 'resume' the actively running session. To do this, replace the entrypoint in the Dockerfile to this:

ENTRYPOINT [ "screen", "-S", "OpenSim", "-D", "-m", "mono",  "./OpenSim.exe" ]

You can now access the OpenSimulator admin prompt by running docker-compose exec metaverse /bin/bash and then running screen -r OpenSim.