Open diffficult opened 4 years ago
@diffficult, I actually have been looking at an issue which I've just raised: https://github.com/SinFulNard/discord-shaxxBot/issues/7
but that seems unrelated to your problem.
I just confirmed I can pull the repo, build the docker image and docker-compose up -d
as intended:
Starting discordshaxxbot_bot_1
I'm using:
Docker version 17.03.2-ce, build f5ec1e2
I'm not familiar with Portainer sorry but that error seems like something is being lost between the build and spinning up the container.
Can you try and tweak the "command" entry in your docker-compose file to be the full path?
Started fresh and now it seems that's working, no error messages anywhere and the bot joined the server it was invited.
Maybe this sounds dumb, but what are the commands that it can read and overall what are the general instructions to use it.
sorry @diffficult, slow response! Glad you got it sorted - does it join the voice chat as expected and make comments?
the bot watches all messages but only responds when the message matches discord_command
. By default its set to the BOT_NAME
ENV var.
So you should be able to do @lordshaxx help
which should trigger this message:
https://github.com/SinFulNard/discord-shaxxBot/blob/master/commands.rb#L60
Followed instructions on repository and the bot failed to start.
I can see that the container is created and Exits (1) and the log I can get for it (from Portainer) is:
If you just run the bot using the interactive shell
docker run -i -t shaxxbot:latest /bin/bash
and after exporting the secret token and the bot name, loads fine and even joins the server it was invited.Don't get what could possibly be wrong if the
docker-compose.yml
file is also giving the sameruby shaxxBot.rb
command I'm using on the interactive bash when running the image alone and executing it manually.