adam/meshcore-hub
1
0 Fork 0
mirror of https://github.com/ipnet-mesh/meshcore-hub.git synced 2026-10-30 19:52:03 +01:00
Code Issues 1 Packages Projects Releases Wiki Activity

Missing default port mapping for web service in docker-compose.yml #42

New Issue
Closed
opened 2026-10-04 23:10:12 +02:00 by adam · 1 comment
adam commented 2026-10-04 23:10:12 +02:00
Owner
Copy link
Copy source

What's wrong?
After running docker-compose --profile all up -d, I can't access the MeshCore Hub website.

Why?
The docker-compose.yml file is missing the ports configuration. The container is running, but it isn't exposing the port to the outside.

Adding the parameter:

ports:
-"8080:8080"

Image

solves the problem

What's wrong? After running `docker-compose --profile all up -d`, I can't access the MeshCore Hub website. Why? The `docker-compose.yml` file is missing the `ports` configuration. The container is running, but it isn't exposing the port to the outside. Adding the parameter: ports: -"8080:8080" <img width="885" height="498" alt="Image" src="https://github.com/user-attachments/assets/fb863afa-0510-4a23-88ef-8cd73d1c5bb7" /> solves the problem <!-- github-sync-id:4322589266 -->
adam closed this issue 2026-10-04 23:10:12 +02:00
adam commented 2026-10-04 23:10:13 +02:00
Author
Owner
Copy link
Copy source

Hello. I was expecting a few teething issues with the new release, so apologies that you aren't have the best experience.

For production environments, its advisable to use a reverse proxy (with TLS), e.g. Traefik, Nginx, Caddy, etc.

But if you want to expose ports directly, you'll have to use the docker-compose.dev.yml as well as the main docker-compose.yml. The dev compose file actually exposes the ports locally. This should be explained in the README (https://github.com/ipnet-mesh/meshcore-hub/blob/main/README.md#docker-compose-profiles), but in short you need to specify both compose files:

# Development (default — exposes ports for local access)
docker compose -f docker-compose.yml -f docker-compose.dev.yml --profile all up -d

The dev compose file actually specifies the exposed ports: https://github.com/ipnet-mesh/meshcore-hub/blob/main/docker-compose.dev.yml

Docker Compose will merge the the ports configuration (from the docker-compose.dev.yml compose file) on top of the standard docker-compose.yml definitions).

I appreciate the feedback and will update the documentation if its unclear.

Hello. I was expecting a few teething issues with the new release, so apologies that you aren't have the best experience. For production environments, its advisable to use a reverse proxy (with TLS), e.g. Traefik, Nginx, Caddy, etc. But if you want to expose ports directly, you'll have to use the `docker-compose.dev.yml` as well as the main `docker-compose.yml`. The `dev` compose file actually exposes the ports locally. This should be explained in the README (https://github.com/ipnet-mesh/meshcore-hub/blob/main/README.md#docker-compose-profiles), but in short you need to specify both compose files: ``` # Development (default — exposes ports for local access) docker compose -f docker-compose.yml -f docker-compose.dev.yml --profile all up -d ``` The `dev` compose file actually specifies the exposed ports: https://github.com/ipnet-mesh/meshcore-hub/blob/main/docker-compose.dev.yml Docker Compose will merge the the `ports` configuration (from the `docker-compose.dev.yml` compose file) on top of the standard `docker-compose.yml` definitions). I appreciate the feedback and will update the documentation if its unclear. <!-- github-comment-id:4313151598 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore-hub#42