Docker Deployment

[Lenaaa-rain]

Hello, I've problem when i want to switching the bot to run in Docker, when use command "docker compose --env-file docker.env up -d --build". the container is running but after 30 mins, nothing happend with the bot, and the bot it's just offline in my server. maybe you can help me with this problem to fix this.

[Bacon-Fixation]

Howdy @MichaelDA123,
my apologize for the absence, life is moving at the speed of life <3

i am curious if you are still having this issue with the docker deployment?
if you are, i have a couple of question in hopes to try narrow it down

are you running this locally or a web service?

what version of docker compose is being used? (should be compatible with v2.xx)

on the machine that is running the container in the directory ./Master-Bot/logs/ is there an error listed in the log file?

is the pc hibernating or going to sleep after 30 min of inactivity?

Much Love
-Bacon

[Lenaaa-rain]

Hi Bacon!! thanks for replying <3. For the docker im using it in WSL on my PC windows, and haven't turn off or hibernated my pc. when i test the bot and running the container, the docker images and the container is running but the isn't online, i've trying couple time to find this issue but still fixed yet.

[PhantomNimbi]

I just tested this myself. I'm having the exact same issue.

There are three warnings in the sources tab. Maybe these are the cause. Not entirely sure, though.

FROM --platform=linux/amd64 node:18-slim
FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/amd64"

ENV PNPM_HOME="/pnpm"

ENV PATH="$PNPM_HOME:$PATH"

ENV NEXT_TELEMETRY_DISABLED 1

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format

WORKDIR "/Master-Bot"



# Ports for the Dashboard  

EXPOSE 3000

ENV PORT 3000

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format



# Install prerequisites and register fonts

RUN apt-get update && apt-get upgrade -y -q && \

    apt-get install -y -q openssl && \

    apt-get install -y -q --no-install-recommends libfontconfig1 && \ 

    npm install -g pnpm 

# Copy files to Container (Excluding whats in .dockerignore)

COPY ./ ./

RUN pnpm install --ignore-scripts && pnpm -F * build 

# If you are running Master-Bot in a Standalone Container and need to connect to a service on localhost uncomment the following ENV for each service running on the containers host

# ENV POSTGRES_HOST="host.docker.internal"

# ENV REDIS_HOST="host.docker.internal"

# ENV LAVA_HOST="host.docker.internal"


# Uncomment the following for Standalone Master-Bot Docker Container Build

# RUN pnpm db:push

# CMD ["pnpm", "-r", "start"]

[PhantomNimbi]

This is being worked on in my current workstream. You can see my progress in the issue below:

• Master-Bot Maintenance & Fix Roadmap #828

[PhantomNimbi]

✅ Update: Docker Deployment — Addressed

The Docker deployment issues described here are addressed in the maintenance work. The Docker and workspace infrastructure was modernized so the containerized bot actually comes online and connects.

---

🔧 What Fixed It

• Docker & Workspace Infrastructure (Stage 2): Updated Dockerfile and docker-compose.yml to Node 20 and pnpm 8.6.7, aligning the containerized build with the versions the bot works on, and verified all workspace build scripts.
• CI/CD Pipeline Alignment (Stage 10): Aligned the workflow with Node 20 + pnpm 8.6.7 for consistent builds.
• Launcher / Service Auto-Detection: The control-panel launchers (scripts/dev.mjs, scripts/start.mjs) now auto-detect and start required services (PostgreSQL, Redis) cross-platform, with a Docker Compose fallback for local database setup — making the "container running but bot offline" scenario much less likely.

Note: The warnings flagged in the previous comment (FROM --platform, legacy ENV key value) came from Dockerfile linting; the migrated Dockerfile uses the current recommended formats.

---

🔗 PR Status

This work is bundled into the open maintenance PR:

PR #829 → #829

• Branch: PhantomNimbi:main
• Status: ✅ Open & Ready for Review
• Summary: feat: modernize monorepo, upgrade Lavalink v4 & cipher, enhance dashboard, and fix auth/tooling

This issue is now resolved pending PR #829's merge.