Tachidesk-Docker Support Thread

[C3004]

New Way to get Rid of the File permission error.

 

I Don't know if this will stick, or if it will get added in the default container.

Create a Backup before adding or removing these Changes.

Don't use this if you made the webui publicly available.

 

They added a function to the development container to change the running user. (https://github.com/Suwayomi/docker-tachidesk/issues/22)

 

Activate advanced view to make these changes

Change **Repository** from "ghcr.io/suwayomi/tachidesk" to "ghcr.io/suwayomi/tachidesk:develop"

Add in **Extra Parameters ** "-u 99:100" without quotations

It should look like this afterwards:

Edited May 6, 2023 by C3004

[Atreides]

Thank you so much for posting this.

[theangelofspace15]

I havent have time to check but it shouldnt be hard by changing the dockerfile. I might yake a look one day. I have not been using tachidesk so I stopped T/Sing.

[Atreides]

I saw a new update, but can't find the change log. Any idea what was changed?

[theangelofspace15]

If you are still having problem. Try this container. `https://hub.docker.com/r/theangelofspace15/tachidesk-server`

 

or change you image to use `theangelofspace15/tachidesk-server`

 

Set

`PUID` to your user id

`PGID` to group id

`/config` to your config file (like: /appdata/tachidesk`

`/config/downloads` to download folder

`/config/local` to local library

the image is based on linuxserver alpine base images so it should use things like docker mods but I havent test it.

Edited June 12, 2023 by theangelofspace15

[Soldius]

On 5/6/2023 at 8:10 AM, C3004 said:

New Way to get Rid of the File permission error.

 

I Don't know if this will stick, or if it will get added in the default container.

Create a Backup before adding or removing these Changes.

Don't use this if you made the webui publicly available.

 

They added a function to the development container to change the running user. (https://github.com/Suwayomi/docker-tachidesk/issues/22)

 

Activate advanced view to make these changes

Change **Repository** from "ghcr.io/suwayomi/tachidesk" to "ghcr.io/suwayomi/tachidesk:develop"

Add in **Extra Parameters ** "-u 99:100" without quotations

It should look like this afterwards:

This fix works for me, but even though I added the environment variable DOWNLOAD_AS_CBZ to true, it does not download into cbz. It keeps the structure as Manga Series > Chapter > images files.

 

 

Does anyone know of a fix for this? Thank you.

[C3004]

16 minutes ago, Soldius said:

This fix works for me, but even though I added the environment variable DOWNLOAD_AS_CBZ to true, it does not download into cbz. It keeps the structure as Manga Series > Chapter > images files.

 

 

Does anyone know of a fix for this? Thank you.

Hi Soldius,

 

That variable is new and currently only in the preview containers.

Please note that the fix only works with the develop container.

 

I wrote about the Fix before the tachidesk guys made a full rewrite of the docker container. The rewrite happened two weeks ago. The Variable you want to use is part of that new rewrite.

As the fix only works in the develop container and the latest update of that one was 18 Days ago the Variable is currently not available in that one.

 

Best Regards

Edited June 12, 2023 by C3004

[Soldius]

1 hour ago, C3004 said:

Hi Soldius,

 

That variable is new and currently only in the preview containers.

Please note that the fix only works with the develop container.

 

I wrote about the Fix before the tachidesk guys made a full rewrite of the docker container. The rewrite happened two weeks ago. The Variable you want to use is part of that new rewrite.

As the fix only works in the develop container and the latest update of that one was 18 Days ago the Variable is currently not available in that one.

 

Best Regards

I followed up on this with a roundabout fix. I switched the docker to "preview container" and used Krusader to go into appdata and change permission of the whole "Tachidesk-Docker" to:

 

 

Basically i just right-click and went into Properties > Permissions.

 

I also did the same thing for the destination download folder to make sure the docker can write into it. This seems to work for me as I am downloading chapters in cbz just fine. Hope this helps someone.

[theangelofspace15]

49 minutes ago, Soldius said:

I followed up on this with a roundabout fix. I switched the docker to "preview container" and used Krusader to go into appdata and change permission of the whole "Tachidesk-Docker" to:

 

 

Basically i just right-click and went into Properties > Permissions.

 

I also did the same thing for the destination download folder to make sure the docker can write into it. This seems to work for me as I am downloading chapters in cbz just fine. Hope this helps someone.

Did you tried my container? Thanks should fix it.  As well. 

[Soldius]

34 minutes ago, theangelofspace15 said:

Did you tried my container? Thanks should fix it.  As well. 

I did! But for some strange reason, nothing loaded. I wiped the appdata and the container data and tried it again but same issues. The webui was not loading for some reason. I gave up after that lol 😆

[theangelofspace15]

2 hours ago, Soldius said:

I did! But for some strange reason, nothing loaded. I wiped the appdata and the container data and tried it again but same issues. The webui was not loading for some reason. I gave up after that lol 😆

Well, i didnt see any comment lol but in case anyone eant to give ot a try this os how it looks. `Config` is your config file, `/config/download` the folder the app downloads manga, `config/local` your local library. 

[Soldius]

Hmm I notice that this is leaking data into my Docker img. My docker went from 32-ish percent to 100% overnight. Here is my mapping:

 

I don't think I miss anything looking at their documentation. I am using the "preview" channel.

[C3004]

57 minutes ago, Soldius said:

Hmm I notice that this is leaking data into my Docker img. My docker went from 32-ish percent to 100% overnight. Here is my mapping:

 

I don't think I miss anything looking at their documentation. I am using the "preview" channel.

Weird. I don't see anything wrong.

 

Do the container Logs currently note any errors?

 

If the container is working correctly set the debug variable to false that the logs don't fill up the docker.img.

 

Just for fun you could also run the docker system df command(https://docs.docker.com/engine/reference/commandline/system_df/)

 

But the debug variable probably filled up the logs.

[Soldius]

3 hours ago, C3004 said:

Weird. I don't see anything wrong.

 

Do the container Logs currently note any errors?

 

If the container is working correctly set the debug variable to false that the logs don't fill up the docker.img.

 

Just for fun you could also run the docker system df command(https://docs.docker.com/engine/reference/commandline/system_df/)

 

But the debug variable probably filled up the logs.

Ohhhhhh, I didn't think the logs were the culprit. Good catch! I will turn it off and try. Thank you!😂

[Soldius]

12 hours ago, C3004 said:

Weird. I don't see anything wrong.

 

Do the container Logs currently note any errors?

 

If the container is working correctly set the debug variable to false that the logs don't fill up the docker.img.

 

Just for fun you could also run the docker system df command(https://docs.docker.com/engine/reference/commandline/system_df/)

 

But the debug variable probably filled up the logs.

Unfortunately, turning the debug log off did not help. Any clue on how to trace down what exactly is filling my docker img? "docker system df: only gives an overview and spaceinvader's scripts gives more detail but only that the container is taking up a large amount of space and not what the space actually is. I also went into the container's console to look at the structure and not able to see any folder with large sizes. I'm stump 🤔

Edited June 14, 2023 by Soldius
Additional troubleshooting info

[Soldius]

9 hours ago, Soldius said:

Unfortunately, turning the debug log off did not help. Any clue on how to trace down what exactly is filling my docker img? "docker system df: only gives an overview and spaceinvader's scripts gives more detail but only that the container is taking up a large amount of space and not what the space actually is. I also went into the container's console to look at the structure and not able to see any folder with large sizes. I'm stump 🤔

Nevermind, I figured it out. Apparently it is using the dir /temp to download the images files and then putting it into the nzb in the "library" folder. This leaves all the images inside the temp folder without cleaning them up afterwards 😑

 

Anyway, I mapped those dir temp like this (remember to change the permission of the folders using Krusader or tachidesk won't be able to write downloads in there): 

 

I may end up just mapping the whole temp folder, since it seems to be creating other things in there. 

 

Another thing i notice is that each time i restart the container, the download list disappeared resulting in me having to re-add the downloads in the GUI. Not sure if this is related.

Edited June 14, 2023 by Soldius

[jtechguru]

On 6/14/2023 at 7:47 AM, Soldius said:

Nevermind, I figured it out. Apparently it is using the dir /temp to download the images files and then putting it into the nzb in the "library" folder. This leaves all the images inside the temp folder without cleaning them up afterwards 😑

 

Anyway, I mapped those dir temp like this (remember to change the permission of the folders using Krusader or tachidesk won't be able to write downloads in there): 

 

I may end up just mapping the whole temp folder, since it seems to be creating other things in there. 

 

Another thing i notice is that each time i restart the container, the download list disappeared resulting in me having to re-add the downloads in the GUI. Not sure if this is related.

So I've gone through and did all of this. However Tachiomi-server still downloads either jpeg, or png. It will not cnvert them to cbz.  I've read the documentation, and cant seem to find the problem. Hoping you could assist in getting it to work proper.

 

[jtechguru]

Does anyone know of a possible solution to Tachideck refusing to download as a cbz?

[C3004]

12 hours ago, jtechguru said:

Does anyone know of a possible solution to Tachideck refusing to download as a cbz?

Please post your Docker Run.

 

Note that i also need to see which repository you're running.

[Soldius]

On 7/10/2023 at 2:06 PM, jtechguru said:

Does anyone know of a possible solution to Tachideck refusing to download as a cbz?

Which branch are you using? I'm using the preview branch.

[gevsan]

Hello.

 

I can't get Tachideck to download as cbz. 

Also I can't get the authorization to work.

 

Here is my docker run and template.

 

 

 

 

[hormonal-rusher2189]

It seems to work, the default install/download and library path needs to be changed to somewhere in your share 

 

You may need to create the directory...

 

It's the simplest way to do it

 

[tknx]

@gevsan did you get this working? I tried your same variable setup and I don't see an option to download as CBZ anywhere appearing.

[Bambusmann]

On 5/6/2023 at 5:10 PM, C3004 said:

New Way to get Rid of the File permission error.

 

I Don't know if this will stick, or if it will get added in the default container.

Create a Backup before adding or removing these Changes.

Don't use this if you made the webui publicly available.

 

They added a function to the development container to change the running user. (https://github.com/Suwayomi/docker-tachidesk/issues/22)

 

Activate advanced view to make these changes

Change **Repository** from "ghcr.io/suwayomi/tachidesk" to "ghcr.io/suwayomi/tachidesk:develop"

Add in **Extra Parameters ** "-u 99:100" without quotations

It should look like this afterwards:

Thank you very much that worked ❤️

Edited February 17 by Bambusmann

[curtdwar]

Suwayomi went v1.0 today. So stable users should be able to update to new features. I've not played with a fresh install to see if permissions issues are ok.

 

What I have worked out is a way to bypass the permissions issues with preview version.

 

What I did was a standard install with preview repository "ghcr.io/suwayomi/tachidesk:preview".

That install will fail due to permissions issue, I then go into midnight commander or krusader and change the appdata directory ("\appdata\Tachidesk-Docker") permissions recursively to everyone full control.

I then go and re-install the docker container and it worked for me.

 

Updates to suwayomi can be applied with a "force update".

 

I'm sure some people won't like the full control permissions, but I don't really care, my Unraid is not exposed to the web.