kevzettler
commented
1 year ago @StuBlad
The title screen should freeze and you'll see this output in the logs:
what logs? browser logs? or some service logs? looks like neohabitat-neohabitat-1 service logs
Error: connect ECONNREFUSED 172.18.0.4:2018 port 2018 is the NEOHABITAT_BRIDGE_ELKO_HOST. For some reason, the connection is being refused.
Can you connect to this port manually with telnet?
I would manually log into the neohabitat-neohabitat-1 container and then manually test that it can make the connection to 172.18.0.4:2018 within the container.
StuBlad
frandallfarmer
AmandaJonesAway
The Docker deployment for NeoHabitat is currently broken. We've been trying to troubleshoot it for a month or two now with varying degrees of success.
Relevant info
Relevant issues to our recent work are: #390 #392
Several PR's were made during this time to update the deployment and get things working again. The first of these commits starts with commit e7c220d.
During this time, we were able to get things operational again and the fork over at https://github.com/AmandaJonesAway/neohabitat successfully works, but somehow with the PR's that got merged, the master repository is still in a broken state. It should be noted that AmandaJonesAway's fork is 15 commits behind master if comparing against it.
Setup
Make sure you have the NeoHabitat installer to test with as it contains a copy of VICE, and the Habitat disk images. You can grab a copy here: https://github.com/StuBlad/neohabitat-installer/releases. If you don't want to use the installer, the disk images are available in the same repository.
Here are the commands I'm using so you can recreate the environment and replicate the broken build.
Ubuntu 22.04 (LTS) x64
It's not building the schema and filling the object database in this current state, so you'll need to modify line 46 in
docker-compose.ymlto true (NEOHABITAT_SHOULD_UPDATE_SCHEMA) and line 49 inrunto true (SHOULD_UPDATE_SCHEMA="${NEOHABITAT_SHOULD_UPDATE_SCHEMA:=true}") before you run sudo docker compose up.You'll only want these set to true for the first time launching this NeoHabitat docker setup to populate the object database. Things will load much faster if you set those configuration options back to false after.
It'll take a few minutes for all the services to come online after bringing the containers up, but when you see the following log output then you are ready to connect to the server:
Go into VICE and Settings > RS232 Settings > RS232 Settings. Set RS232 Device 1 to the IP of the NeoHabitat server and port 1986 (127.0.0.1:1986) for example.
Load
Habitat-Boot.d64. Press return on the title screen. Type in the name you want for your avatar and press return. When on the main Habitat title screen, press Alt-N and any key and watch the server output.The actual problem
The title screen should freeze and you'll see this output in the logs:
According to the file
docker-compose.yml, port 2018 is theNEOHABITAT_BRIDGE_ELKO_HOST.For some reason, the connection is being refused. When this setup previously worked, we used ip addresses instead of giving a container a name and referring to that instead. I'm wondering if this is what has caused the issue here. We need this port to be accessible and responsive in order to have this Docker setup working again.