Djoss

The problem seems to be related to the font used. Did you change it the the profile ? Can you try to edit the profile and see what is configured ? Not sure why it gives an error now, since nothing related to that changed from the last version...

Looks like JDownloader is running now ?

Are you connecting using an existing profile ?

Could you provide the output of: docker exec JDownloader2 ps

The template had incorrect default values for these settings. This is now fixed. If you prefer to set the credentials from JDownloader, just make sure to clear the incorrect default values from container's settings.

Ok, the Docker image has been updated with this new version!

Which issue exactly you are referring to ?

How do you set credentials ? Via the JDownloader interface or via environment variables ?

Did you try to remove and re-create the container ?

This is expected. /storage is a different mount mapped to /mnt/user in unRAID. Other files and folders are from the Docker image itself.

Humm this command should output something... Did you run "docker exec CloudBerryBackup mount" ?

Yes sorry, I wanted to see the output of the command.

The mount type for "/" is different in both cases. Since CloudBerry Backup seems to work by mount point, it is possible that it doesn't recognize it. Under XFS, can you try to run "docker exec CloudBerryBackup mount" ? From the app's point of view, it's not really important if it is running in a container or not. However, support might be quick to close your case by answering that running in a container is not officially supported.

You should probably try to contact CloudBerry support about this. No need to indicate that you are using a Docker container. Just tell that the root folder "/" is missing from the Backup source.

Great!

What about: ls -la /mnt/user/appdata/JDownloader2/ Did you try to remove and re-create the container ?

And this one: ls -ld /mnt/user/appdata/JDownloader2

Can you share the output of the following command: docker inspect JDownloader2

I'm sure there is a way... you may have more suggestions by asking somewhere else in the forum. If you are using the free license of CloudBerry Backup, could you run it also on your second server ?

To my knowledge CloudBerry Backup does not support FTP as a backup source. Only files from the local filesystem.

The following message is "normal" and does not indicate a problem: [cbbLocalManagement] [ CBB ] [ 1 ] Error on remove old icon file, path: /opt/local/CloudBerry Backup/share/webAccess/img/MainIcon.ico error: Permission denied It's this one that is problematic: [supervisor ] service 'cbbLocalManagement' failed to be started: not ready after 5000 msec, giving up. Did you see the error once and reverted to the previous version?

Can you try to run the following command to verify if you see the same problem: docker run --rm jlesage/cloudberry-backup

CloudBerry Backup was always picky on how it shows the directory tree. It seems to be based on mounts. Using different Docker image type changes the mount type used inside the container. Some mount types don't seem to be recognized by CloudBerry Backup.

Yes, I'm working on this.

Yes, fixed with the latest image. Sorry about that.