Closed szentigrad3 closed 1 month ago
fix your docker. check if your docker is running
fix your docker. check if your docker is running
docker is running
fix your docker. check if your docker is running
docker is running
^^ i do some search and found that article. it might be an issue with your docker-compose
fix your docker. check if your docker is running
docker is running
^^ i do some search and found that article. it might be an issue with your docker-compose
e.g. docker compose and not like you used to docker-compose (dash separated).
New Command
docker compose ....
run make stop
and run make start
again. this usually happened because lavalink take long time to boot up
run
make stop
and runmake start
again. this usually happened because lavalink take long time to boot up
didn't work tried multiple times
did you make any changes on application.yml? like changing the lavalink password ?
did you make any changes on application.yml? like changing the lavalink password ?
no changes
hm thats weird. mine just work fine. can you run the bot without lavalink using make start-noll
and host the lavalink seperately. I will try to fix docker-compose settings later
Oh anyway here are my docker and docker-compose version
Oh anyway here are my docker and docker-compose version
can you try change the settings on docker-compose.yml
?
healthcheck:
test: 'curl -H "Authorization: youshallnotpass" -s http://localhost:2333/version || exit 1'
interval: 10s
timeout: 10s
retries: 3
start_period: 120s # Delay before starting checks
change retries: 5
and start_period: 10s
and after that you run make stop
and make start
can you try change the settings on
docker-compose.yml
?healthcheck: test: 'curl -H "Authorization: youshallnotpass" -s http://localhost:2333/version || exit 1' interval: 10s timeout: 10s retries: 3 start_period: 120s # Delay before starting checks
change
retries: 5
andstart_period: 10s
and after that you runmake stop
andmake start
yaml: line 15: did not find expected key
uhh nvm just copy this and paste it to your docker-compose.yml. remember you need to remove existing docker container and make sure there is no lavalink running on port 2333
services:
lavalink:
container_name: lavalink
image: ghcr.io/lavalink-devs/lavalink
restart: on-failure
hostname: docker.lavalink
volumes:
- ./lavalink/application.yml:/opt/Lavalink/application.yml
- ./lavalink/plugins:/opt/Lavalink/plugins
healthcheck:
test: 'curl -H "Authorization: youshallnotpass" -s http://localhost:2333/version || exit 1'
interval: 10s
timeout: 10s
retries: 5
start_period: 10s # Delay before starting checks
ports:
- "2333:2333" # Expose port for other containers or external access if needed
musicbot:
container_name: musicbot
build:
context: .
target: musicbot
ports:
- "3000:3000" # Not required
volumes:
- ./src:/app/src # Mount code directory
environment:
- NODE_ENV=production # Set your environment variables if needed
restart: unless-stopped
depends_on:
lavalink:
condition: service_healthy
uhh nvm just copy this and paste it to your docker-compose.yml. remember you need to remove existing docker container and make sure there is no lavalink running on port 2333
services: lavalink: container_name: lavalink image: ghcr.io/lavalink-devs/lavalink restart: on-failure hostname: docker.lavalink volumes: - ./lavalink/application.yml:/opt/Lavalink/application.yml - ./lavalink/plugins:/opt/Lavalink/plugins healthcheck: test: 'curl -H "Authorization: youshallnotpass" -s http://localhost:2333/version || exit 1' interval: 10s timeout: 10s retries: 5 start_period: 10s # Delay before starting checks ports: - "2333:2333" # Expose port for other containers or external access if needed musicbot: container_name: musicbot build: context: . target: musicbot ports: - "3000:3000" # Not required volumes: - ./src:/app/src # Mount code directory environment: - NODE_ENV=production # Set your environment variables if needed restart: unless-stopped depends_on: lavalink: condition: service_healthy
i have noticed this ✔ lavalink 8 layers [⣿⣿⣿⣿⣿⣿⣿⣿] 0B/0B Pulled also same problem
is the lavalink container running now? if not can you try check the logs using docker logs lavalink
is the lavalink container running now? if not can you try check the logs using
docker logs lavalink
ah no wonder docker do not have enough permissions to create plugins folder for lavalink
you need to set permissions 777
to music bot folder
you need to set permissions
777
to music bot folder
woot loaded now
i cant really understand what you trying to say right now
its working
alright good to hear that, ill close this issue and feel free to reopen if you have any issues :D