From 9be7e5e27bb7fc9b98b27f4a8fab88177a5d34dd Mon Sep 17 00:00:00 2001 From: Casey LP Date: Mon, 30 Jan 2023 09:14:27 +0000 Subject: [PATCH] Update README.md --- README.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README.md b/README.md index 17d1a01..69bf034 100644 --- a/README.md +++ b/README.md @@ -33,6 +33,27 @@ Once the server is running, you should be able to connect to it on `localhost:90 If you don't define otherwise in the environments or a custom configuration, the login username is **Foo bar** and the password is **password**. +## Limitations + +At current, there doesn't appear to be an implemented and/or documented approach to managing the server from _outside_ the active TTY, and running `docker attach opensim` seems to produce a blank prompt. You can `exec` into the container or edit the bound configuration script and restart the server to make changes, but in some server instances you might need to intercept the prompt. + +Until a better solution is made, you can get crafty with `screen` to get access to the current prompt in terminal, with the caveat that logging will no longer work. + +You can achieve this with a **Dockerfile** like so: + +```dockerfile +FROM soupbowl/opensimulator:edge +CMD [ "screen", "-S", "OpenSim", "-D", "-m", "mono", "./OpenSim.exe" ] +``` + +With a container running the above Dockerfile, you can access a controllable OpenSimulator administration prompt by running: + +``` +docker exec -it screen -r OpenSim +``` + +You can leave the screen session by pressing `ctrl + a` then `d`. + ## Examples See [this repository](https://github.com/soup-bowl/opensim-sandbox) for some example usages of this image.