[GH-ISSUE #1087] Docker MeshCentral container does not start #2613

New issue

Closed

opened 2026-03-14 04:49:49 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 04:49:49 +03:00

Owner

Originally created by @kmccmk9 on GitHub (Apr 24, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1087

Server Info (please complete the following information):

OS: Ubuntu 20.04
Browser: Firefox
RMM Version: Latest

Installation Method:

Standard
Docker

Agent Info (please complete the following information):

Agent version: NA
Agent OS: NA

Describe the bug
When running the docker compose file on a vanilla first time install, meshcentral container never starts up and repeatedly prints. "waiting for nginx to start...". Upon further inspection, this happens because the entrypoint.sh file has a hardcoded ip address that is not within the subnet created for this stack. Therefore the meshcentral container will never be able to communicate with the nginx container and this causes other containers that depend on meshcentral to fail as well.

To Reproduce
Steps to reproduce the behavior:

Download the docker compose file from this repository
Create a valid .env file from this repository
Start the compose file as documented
Check the logs for the init container and you will see it is waiting for the meshcentral container.
Check the logs for the meshcentral container and you will see it can't connect to the nginx container.

Expected behavior
The containers should be on the same network or the entrypoint.sh should have a configurable environment variable to control the nginx IP

Screenshots
NA

Additional context
The current workaround is to acquire a shell of the running container and modify the entrypoint.sh file yourself.

Originally created by @kmccmk9 on GitHub (Apr 24, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1087 **Server Info (please complete the following information):** - OS: Ubuntu 20.04 - Browser: Firefox - RMM Version: Latest **Installation Method:** - [ ] Standard - [X] Docker **Agent Info (please complete the following information):** - Agent version: NA - Agent OS: NA **Describe the bug** When running the docker compose file on a vanilla first time install, meshcentral container never starts up and repeatedly prints. "waiting for nginx to start...". Upon further inspection, this happens because the entrypoint.sh file has a hardcoded ip address that is not within the subnet created for this stack. Therefore the meshcentral container will never be able to communicate with the nginx container and this causes other containers that depend on meshcentral to fail as well. **To Reproduce** Steps to reproduce the behavior: 1. Download the docker compose file from this repository 2. Create a valid .env file from this repository 3. Start the compose file as documented 4. Check the logs for the init container and you will see it is waiting for the meshcentral container. 5. Check the logs for the meshcentral container and you will see it can't connect to the nginx container. **Expected behavior** The containers should be on the same network or the entrypoint.sh should have a configurable environment variable to control the nginx IP **Screenshots** NA **Additional context** The current workaround is to acquire a shell of the running container and modify the entrypoint.sh file yourself.