saarg

Then you have removed the original one and added a new yourself. Next time this happens, remove the one you have added and change the port in the one CA adds.

If port 80 is taken, then simply use another port. That's what port mapping is for.

I guess noone within the team is in their right mind. It does not prevent you from auto-updating.

Problem is that Nvidia doesn't support musl based systems, so their drivers doesn't work in our alpine baseimage. I think there might be a dirty workaround out there, but I'd rather rebase it to Ubuntu then. I'll look into it when I get enough time. So no timeline.

Not after every update. There is a date on top of the file so you can check it yours is up to date or not. We might also have added a check that outputs any outdated files in the log. Not sure if we added it to nextcloud or its only in swag.

You might have to stop calibre for Calibre-web to pick up the books.

Ke?

Why do you think it saves the images inside the container?

Restart the Calibre-web container. I think there was some issues when you have both calibre and Calibre-web running at the same time. As far as I know, you don't need Calibre after setting up Calibre-web.

None

Swag can't connect to what you are proxying.

The first post on this page has the link to GitHub.

It's all in the readme on github.

It doesn't make any sense to run it in its own custom network if you have no reason to.

You need to port forward port 80 to 180 and 443 to 4433. From your screenshots it looks like you only port forward 180 to 180 and 4433 to 4433. That will not work.

Looks like your portforwarding is missing. You need to port forward 80 & 443 to 180 & 4433 on 192.168.1.50

We have never ever made a mistake 😎

It maps the port inside the container to your host, the same way as you are able to connect to calibre. This is one of the most basic things about docker.

You can use the customization option we have. Read this blog post

I didn't know if we made a template or not, so that's the reason I asked if you searched in CA.

No. We already have new container for hedgedoc. Have you searched CA for it? Unsure of you can just change the repo and "upgrade", in case you want to test it, backup your appdata first.

Or you could have simply mapped the port the content server use.

No

As we have said earlier, Kodi headless is not doing that. Read what alturismo wrote. Set up Jellyfin/Emby and you will get what you want. For the naming issues, just follow the naming that is the "industry" standard and you will rarely have issues getting movies/TV shows correctly identified.

Why do you need to set up Kodi on unraid? If you want to watch the content, then set up a VM and add a GPU to the VM and connect it to the display. There is nothing ideal about running Kodi I'm side a container through vnc/RDP. What exactly are you looking for?