Support Tread for:

 

Docker Container:

-Nadekobotv4

Repository:

https://github.com/disbedan015/nadekobotv4-unraid

 

Docker Hub: https://hub.docker.com/repository/docker/disbedan015/nadekobotv4
GitHub: https://github.com/disbedan015/

Nadekobot will pretty much work as long as you set the discord bot token and the owner ID but it supports a lot of other optional api keys you can add.

 

Full list of supported commands are available here https://nadeko.bot/commands
Original project GitLab page https://gitlab.com/Kwoth/nadekobot
Docker image file is built from https://github.com/disbedan015/NadekoBotv4-Docker

Hey, thanks for creating a docker container for Nadeko, been running great so far.

 

Sorry for the potentially noob question: I know on the Windows version you are able to get more customization out of the bot by editing the appropriate [config-name].yml file, but I was wondering where those YAML files were actually located so that they could be updated.

 

Thanks!

@Yeoubi Not a dumb question at all I had to edit the template a little bit to make that work. I have updated it by default now. Since you already have it you will want to add a add a path to the config

 

You can do this by editing the container.

Scroll to the bottom and click on Add another path, port, variable, label, or device.

 

It will be a Path

You can name it what ever I choose nadeko

container path must be /nadeko

Host path can be where ever you'd like the bot information to be saved on your unraid. You will edit the yaml files here

default value can be left blank

access mode I have it as Read/Write - Shared but normal read/write should also work.

 

Save your path and click Done at the bottom of the edit screen. After it restarts the folder should be populated and let you edit the yaml. For the bot to see the changes it will need restarted. You can do this with the Die command or restarting the container one more time. 

 

Please feel free to ask if you have any questions.

 

Hey again, great work as always with updating the bot to 6.x.

Ran into an issue when upgrading where I can't set the timezone, as the .timezones command returns a null value, shown below:

I thought maybe adding a TimeZoneDB api key would resolve the issue, but that doesn't seem to have affected anything.

I migrated from the last build of the nadekobotV4 (I guess currently it's called nadekobotv5.39) that's on the Community Apps, but I don't see any reason as to why migrating any yml files would break that functionality.

It seems this is an issue with the base config, as loading the docker with just my Discord Bot Token and not transferring the yml files from my last build results in the same behavior.

Not sure if this is also an issue with the normal Windows build of Nadeko and I've asked in the public help Discord with no response, so I figured I might as well ask here as well.

@Yeoubi

I’m not entirely sure since I am no longer making a custom docker image I’m using the stock image and just set up a template based on the official v6 image they provided. I do agree it’s likely an issue with the image because my bot has the same behavior when tested. I do have a possible idea that I will test when I have some time tomorrow but if you want to test it that’s fine. Add an additional variable to the template for “TZ” and set it to the correct timezone that way as an example “America/New_York” since that’s the default way to do it with docker. https://wikipedia.org/wiki/List_of_tz_database_time_zones. I’ll get back to you with hopefully good news soon.

Got some free time myself to try, so I've gone ahead and tested by explicitly stating the TZ variable like you were thinking about doing, and it doesn't seem to change anything on the bot's end.

Don't think I set them up improperly, but here are some screenshots from my attempt:

@Yeoubi Thanks for checking that for me. I finally got done with work and had some time to explore. It looks like tzdata isn't installed by default in the base docker image they are using. I'm working on submitting a fork to fix this thru github however for your issue to resolve right away it's pretty simple. I've included the steps below. Let me know if you have any trouble.

Open the Nadekobotv6 console.

type in
apk add -U tzdata

restart the docker container

the command will now work

You can watch this incident to see if, I was wrong or if they need any additional information.
https://github.com/nadeko-bot/nadekobot/issues/15

Fix looks good to me, didn't think about adding tzdata to the docker image itself.

Hopefully it gets merged without any pushback, otherwise they might just need to update their Docker installation instructions.