Error creating bean with name 'pluginManager'

[wooden magnet]

lavalink | Caused by: java.io.FileNotFoundException: ./plugins/jiosaavn-plugin-0.1.7.jar (Permission denied)

fix your permissions.

https://lavalink.dev/configuration/docker.html

[delicate viper]

I seem to have corrected the problem, but it tells me to go under the new version of source.youtube, but I’m already under the 1.8.3

[wooden magnet]

is that the full log?

[delicate viper]

yes

[wooden magnet]

doesn't look so to me

the start with the plugins is missing

[delicate viper]

yet nothing else charges

[wooden magnet]

send as text.

this is terrible to read

[wooden magnet]

for me it looks like your config is not applied

it doesn't even download/check the plugins you set

[delicate viper]

services:
  lavalink:
    # pin the image version to Lavalink v4
    image: ghcr.io/lavalink-devs/lavalink:4
    container_name: lavalink
    restart: unless-stopped
    environment:
      # set Java options here
      - _JAVA_OPTIONS=-Xmx6G
      # set lavalink server port
      - SERVER_PORT=2333
      # set password for lavalink
      - LAVALINK_SERVER_PASSWORD=youshallnotpass
    volumes:
        # mount application.yml from the same directory or use environment variables
        - ./lavalink/application.yml:/opt/lavalink/application.yml
        # persist plugins between restarts, make sure to set the correct permissions (user: 322, group: 322)
        - ./lavalink/plugins/:/opt/lavalink/plugins/
    networks:
      - lavalink
    expose:
      # lavalink exposes port 2333 to connect to for other containers (this is for documentation purposes only)
      - 2333
    ports:
      # you only need this if you want to make your lavalink accessible from outside of containers
      - "2333:2333"
networks:
  # create a lavalink network you can add other containers to, to give them access to Lavalink
  lavalink:
    name: lavalink

The component docker respects the default one. I just added a folder

[wooden magnet]

it's /opt/Lavalink

not /opt/lavalink

[delicate viper]

Does it really make a difference?

[wooden magnet]

if you mount your appliation.yml you don't need to set the SERVER_PORT & LAVALINK_SERVER_PASSWORD environment variables

[wooden magnet]

https://tryitands.ee/

[delicate viper]

services:
  lavalink:
    # pin the image version to Lavalink v4
    image: ghcr.io/lavalink-devs/lavalink:4
    container_name: lavalink
    restart: unless-stopped
    environment:
      # set Java options here
      - _JAVA_OPTIONS=-Xmx6G
    volumes:
      # mount application.yml from the same directory or use environment variables
      - ./Lavalink/application.yml:/opt/Lavalink/application.yml
      # persist plugins between restarts, make sure to set the correct permissions (user: 322, group: 322)
      - ./Lavalink/plugins/:/opt/Lavalink/plugins/
    networks:
      - lavalink
    expose:
      # lavalink exposes port 2333 to connect to for other containers (this is for documentation purposes only)
      - 2333
    ports:
      # you only need this if you want to make your lavalink accessible from outside of containers
      - "2333:2333"
networks:
  # create a lavalink network you can add other containers to, to give them access to Lavalink
  lavalink:
    name: lavalink

Respect what you say to me?

[wooden magnet]

what?

[delicate viper]

this

[wooden magnet]

yes and?

./Lavalink/application.yml:/opt/Lavalink/application.yml
the first path doesn't matter

that can be lower case

that's whatever is on your local disk

I have no idea what you mean with

Respect what you say to me?

[delicate viper]

services:
  lavalink:
    # pin the image version to Lavalink v4
    image: ghcr.io/lavalink-devs/lavalink:4
    container_name: lavalink
    restart: unless-stopped
    environment:
      # set Java options here
      - _JAVA_OPTIONS=-Xmx6G
    volumes:
      # mount application.yml from the same directory or use environment variables
      - ./Lavalink/application.yml:/opt/Lavalink/application.yml
      # persist plugins between restarts, make sure to set the correct permissions (user: 322, group: 322)
      - ./Lavalink/plugins/:/opt/Lavalink/plugins/
    networks:
      - lavalink
    expose:
      # lavalink exposes port 2333 to connect to for other containers (this is for documentation purposes only)
      - 2333
    ports:
      # you only need this if you want to make your lavalink accessible from outside of containers
      - "2333:2333"
networks:
  # create a lavalink network you can add other containers to, to give them access to Lavalink
  lavalink:
    name: lavalink

I solved the problem, but I still have no plugin that seems to load

[04/10/2024] [20:52:19] [antiCrash.js] [Lavamusic] » ✖  error     Unhandled Rejection at: Promise {
  <rejected> Error: Lavalink Node has not 'youtube' enabled, which is required to have 'ytmsearch' work
      at ManagerUtils.validateSourceString (C:\Users\LucasB25\Documents\GitHub\Panaisdev\node_modules\lavalink-client\dist\index.js:844:13)
      at LavalinkNode.search (C:\Users\LucasB25\Documents\GitHub\Panaisdev\node_modules\lavalink-client\dist\index.js:1127:62)
      at Player.search (C:\Users\LucasB25\Documents\GitHub\Panaisdev\node_modules\lavalink-client\dist\index.js:3981:22)
      at Play.run (C:\Users\LucasB25\Documents\GitHub\Panaisdev\dist\commands\Music\Play.js:60:40)
      at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
} reason: Error: Lavalink Node has not 'youtube' enabled, which is required to have 'ytmsearch' work
    at ManagerUtils.validateSourceString (C:\Users\LucasB25\Documents\GitHub\Panaisdev\node_modules\lavalink-client\dist\index.js:844:13)
    at LavalinkNode.search (C:\Users\LucasB25\Documents\GitHub\Panaisdev\node_modules\lavalink-client\dist\index.js:1127:62)
    at Player.search (C:\Users\LucasB25\Documents\GitHub\Panaisdev\node_modules\lavalink-client\dist\index.js:3981:22)
    at Play.run (C:\Users\LucasB25\Documents\GitHub\Panaisdev\dist\commands\Music\Play.js:60:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

What makes that side bot, it can not find the source activated

[wooden magnet]

nice google account

[delicate viper]

yees

[wooden magnet]

run this perhaps

docker exec lavalink cat /opt/Lavalink/application.yml

and see the config

[delicate viper]

exactly the same

[wooden magnet]

to me it still looks your config is not being applied

can you show your folders where the stuff is in?

[wooden magnet]

lavalink still has no perms to write to the plugins folder as far as I can tell

that should result in the same error as previously tho

¯_(ツ)_/¯

[delicate viper]

ah yes

good now, go added the bot. Question is it a good thing to put the bot in the same docker-compose.yml as the lavalink?

[wooden magnet]

That's a fine thing to do

One compose file = one project

[viscid kettle]

now agree pm2 is better

[wooden magnet]