Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Problem]: Container on QNAP NAS: Backitup can't access mount point #438

Closed
n-albrecht opened this issue Feb 5, 2024 · 2 comments
Closed

Comments

@n-albrecht
Copy link

Description / Beschreibung

Hi, I have installed iobroker as a docker container on a QNAP NAS. Everything works fine so far, except backups.
I have set up a new user "iobroker" in the NAS and given it permissions to a certain folder (/Container/iobroker).
In portainer, I have mounted the remote folder as an additional volume to the container.
SSHing into the container, I have read/write access to the folder (I've mounted it in the container to /root/backup).
However, Backitup in iobroker does not work, it creates the backup files to /opt/iobroker/backups and when trying to copy that to /root/backup, it says
[ERROR] [cifs] - Path "/root/backup/" not found
I've also tried to mount the NAS folder via CIFS, but here I get

[DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=iobroker,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=2.0 //192.168.178.120/Container/iobroker/backups/ /opt/iobroker/backups"
[DEBUG] [mount] - first mount attempt with smb option failed. try next mount attempt without smb option ...
[DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=iobroker,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.178.120/Container/iobroker/backups/ /opt/iobroker/backups"
[ERROR] [mount] - [undefined Error: Command failed: sudo mount -t cifs -o username=iobroker,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.178.120/Container/iobroker/backups/ /opt/iobroker/backups
Unable to apply new capability set.

Trying to manually mount from within the Container using
mount -t cifs -o username=iobroker,password=[password],rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.178.120/Container/iobroker/backups/ /mnt/Container/
also gives me the "Unable to apply new capability set." error

192.168.178.120 is the IP of my NAS. User iobroker is also in a group of that name and has permissions to the /Container
I've restarted the container several times already.
Any ideas?

Also, I found out that this link from the documentation isnot working:
https://docs.buanet.de/projects/iobroker-docker-image/docs_backitup.html

Image version

v9.0.1

Docker logs / Docker Protokoll

Actions

      

Checking Database connection... Done.

 

 

--------------------------------------------------------------------------------

-------------------------     2024-02-05 15:19:40      -------------------------

--------------------------------------------------------------------------------

-----                                                                      -----

----- ██╗  ██████╗  ██████╗  ██████╗   ██████╗  ██╗  ██╗ ███████╗ ██████╗  -----

----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ -----

----- ██║ ██║   ██║ ██████╔╝ ██████╔╝ ██║   ██║ █████╔╝  █████╗   ██████╔╝ -----

----- ██║ ██║   ██║ ██╔══██╗ ██╔══██╗ ██║   ██║ ██╔═██╗  ██╔══╝   ██╔══██╗ -----

----- ██║ ╚██████╔╝ ██████╔╝ ██║  ██║ ╚██████╔╝ ██║  ██╗ ███████╗ ██║  ██║ -----

----- ╚═╝  ╚═════╝  ╚═════╝  ╚═╝  ╚═╝  ╚═════╝  ╚═╝  ╚═╝ ╚══════╝ ╚═╝  ╚═╝ -----

-----                                                                      -----

-----              Welcome to your ioBroker Docker container!              -----

-----                    Startupscript is now running!                     -----

-----                          Please be patient!                          -----

--------------------------------------------------------------------------------

 

--------------------------------------------------------------------------------

-----                          System Information                          -----

-----                    arch:                x86_64                       -----

-----                    hostname:            iobroker                     -----

-----                                                                      -----

-----                          Version Information                         -----

-----                    image:               v9.0.1                       -----

-----                    build:               2023-12-24T23:44:38+00:00    -----

-----                    node:                v18.19.0                     -----

-----                    npm:                 10.2.3                       -----

-----                                                                      -----

-----                        Environment Variables                         -----

-----                    SETGID:              1000                         -----

-----                    SETUID:              1000                         -----

--------------------------------------------------------------------------------

 

--------------------------------------------------------------------------------

-----                   Step 1 of 5: Preparing container                   -----

--------------------------------------------------------------------------------

 

Updating Linux packages on first run... Done.

 

 

 

Registering maintenance script as command... Done.

 

--------------------------------------------------------------------------------

-----             Step 2 of 5: Detecting ioBroker installation             -----

--------------------------------------------------------------------------------

 

Existing installation of ioBroker detected in "/opt/iobroker".

 

--------------------------------------------------------------------------------

-----             Step 3 of 5: Checking ioBroker installation              -----

--------------------------------------------------------------------------------

 

(Re)setting permissions (This might take a while! Please be patient!)... Done.

 

Checking Database connection... Done.

 

Hostname in ioBroker matches the hostname of this container.

No action required.

 

--------------------------------------------------------------------------------

-----                Step 4 of 5: Applying special settings                -----

--------------------------------------------------------------------------------

 

Some adapters have special requirements/ settings which can be activated by the use of environment variables.

For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).

 

 

--------------------------------------------------------------------------------

-----                    Step 5 of 5: ioBroker startup                     -----

--------------------------------------------------------------------------------

 

Starting ioBroker... 

 

##### #### ### ## # iobroker.js-controller log output # ## ### #### #####

host.iobroker check instance "system.adapter.admin.0" for host "iobroker"

host.iobroker check instance "system.adapter.history.0" for host "iobroker"

host.iobroker check instance "system.adapter.influxdb.0" for host "iobroker"

host.iobroker check instance "system.adapter.javascript.0" for host "iobroker"

host.iobroker check instance "system.adapter.mqtt.0" for host "iobroker"

host.iobroker check instance "system.adapter.modbus.0" for host "iobroker"

host.iobroker check instance "system.adapter.discovery.0" for host "iobroker"

host.iobroker check instance "system.adapter.backitup.0" for host "iobroker"

host.iobroker check instance "system.adapter.ble.0" for host "iobroker"

Send diag info: {"uuid":"1210dd27-bca3-4917-b368-6b4f4fbd90c8","language":"de","country":"Germany","hosts":[{"version":"5.0.17","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.19.0","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.12.0","platform":"Javascript/Node.js"},"discovery":{"version":"4.2.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.9.8","platform":"Javascript/Node.js"},"history":{"version":"3.0.1","platform":"Javascript/Node.js"},"mqtt":{"version":"5.1.0","platform":"Javascript/Node.js"},"modbus":{"version":"6.0.1","platform":"Javascript/Node.js"},"influxdb":{"version":"3.2.0","platform":"Javascript/Node.js"},"javascript":{"version":"7.1.6","platform":"Javascript/Node.js"},"ble":{"version":"0.13.4","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":9,"compactMode":false,"noCompactInstances":0,"model":"Intel(R) Celeron(R) J4125 CPU @ 2.00GHz","cpus":4,"mem":33500057600,"ostype":"Linux","city":"[city]"}

================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging]

Please translate in words.js: Backup error on: 


Please translate in words.js: Backup error on: 


Please translate in words.js: Backup error on: 


Please translate in words.js: Backup error on: 


Please translate in words.js: Backup error on: 


Please translate in words.js: Backup error on:
@n-albrecht
Copy link
Author

Edited the topic, my bad, apologies

@n-albrecht n-albrecht changed the title Container on QNAP NAS: Backitup can't access mount point [Problem]: [Problem]: Container on QNAP NAS: Backitup can't access mount point Feb 7, 2024
@buanet
Copy link
Owner

buanet commented Feb 7, 2024

As this seems not to be a issue, I`ll convert this into a discussion.

Regards,
André

Repository owner locked and limited conversation to collaborators Feb 7, 2024
@buanet buanet converted this issue into discussion #439 Feb 7, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants