James Tufarelli

Hi, It seems like Nautical is attempting to backup itself. I have some steps in place to prevent this but it seems like that isn't working. Could you add the...

Thanks for sending me the logs. I think I may have misunderstood your issue before. Based on these logs, I can see that Nautical is not trying to back itself...

It looks like the `-1` is coming from the *project name* of the Docker compose project? Source; https://stackoverflow.com/questions/33045358/docker-compose-image-named-prefix-s-1-instead-of-s I haven't encountered this before myself, but you may need to do...

Hi @IanWardell, Are you able to share some of your container configs as well? I'm wondering if you need to apply the `container_name` property to each of your containers.

Yeah it would be helpful if you could list out a few of your compose files. I am mostly looking to see how you mount your *volumes* to each of...

Hi, Could you set the log level to `TRACE` and attach your Nautical config and logs as well as one of the skipped container's config. Is it skipping all containers?...

Ahh okay I think I understand. It seems like the `nautical-backup.enable` label is working properly. The issue seems to be that the `/app/source/paperless-webserver-1` doesn't exist inside Nautical. Take a look...

> However, nautical-backup seems to be looking for the volume to be the same name as the container? Yes, this is the default action, but you have a few options...

I'm closing this issue since it's so old. Please re-open if it's still relevant.

Hmm, not by default. I think you could add the [Additional Folders](https://minituff.github.io/nautical-backup/arguments/#additional-folders) variable and use that to go to a second location. You could also use the [Lifecycle hooks](https://minituff.github.io/nautical-backup/labels/?h=life#lifecycle-hooks) to...