[HowTo] ioBroker unter Docker auf Synology DiskStation
-
@glasfaser sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
...einen einfachen Fix?
Nein , Meldung nicht beachten !
...aber das Backup wird nicht 'umgesetzt'
-
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
...aber das Backup wird nicht 'umgesetzt'
Hat aber nicht´s mit dieser Meldung zu tun.
Was ich nicht verstehe , wo hast du die Ausgabe her , das nur zwave erscheint , obwohl oben nur drei Adapter zu sehen sind ?
Adapter "zwave2" : 1.9.3 root@RasPi4b:/opt/iobroker# iobroker version -
@glasfaser sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
...aber das Backup wird nicht 'umgesetzt'
Hat aber nicht´s mit dieser Meldung zu tun.
Was ich nicht verstehe , wo hast du die Ausgabe her , das nur zwave erscheint , obwohl oben nur drei Adapter zu sehen sind ?
Adapter "zwave2" : 1.9.3 root@RasPi4b:/opt/iobroker# iobroker versionDas hab ich nur abgehackt.
alle Adapter sind aufgelistet.Meine Thread war eh schon so lang
-
root@RasPi4b:/opt/iobroker# iobroker update Used repository: stable hash unchanged, use cached sources update done Adapter "admin" : 4.2.1 , installed 4.2.1 Adapter "alarm" : 2.0.1 Adapter "alexa2" : 3.9.0 Adapter "alias-manager" : 1.2.1 Adapter "alpha2" : 1.0.0 Adapter "amazon-dash" : 1.1.0 Adapter "artnet" : 1.2.2 Adapter "asterisk" : 1.0.6 Adapter "asuswrt" : 1.0.1 Adapter "b-control-em" : 0.2.1 Adapter "backitup" : 2.1.11 , installed 2.1.11 Adapter "beckhoff" : 1.4.0 Adapter "benq" : 0.2.4 Adapter "binance" : 1.1.3 Adapter "ble" : 0.12.0 Adapter "bluelink" : 1.0.4 Adapter "bmw" : 1.3.3 Adapter "bosesoundtouch": 0.9.3 Adapter "botvac" : 1.0.0 Adapter "bring" : 1.7.7 Adapter "broadlink2" : 2.0.3 Adapter "bsblan" : 0.2.2 Adapter "bshb" : 0.1.13 Adapter "bydbatt" : 1.0.5 Adapter "chromecast" : 2.3.1 Adapter "cloud" : 4.0.10 Adapter "comfoair" : 1.1.3 Adapter "contactid" : 1.0.2 Adapter "coronavirus-statistics": 0.6.3 Adapter "countdown" : 1.2.3 Adapter "cul" : 1.3.5 Adapter "daikin" : 1.3.1 Adapter "daswetter" : 3.0.7 Adapter "deconz" : 1.3.11 Adapter "denon" : 1.10.7 Adapter "device-reminder": 1.2.1 Adapter "devices" : 0.3.16 Adapter "digitalstrom" : 2.2.0 Adapter "discovergy" : 0.5.4 Adapter "discovery" : 2.6.1 , installed 2.6.1 Adapter "divera247" : 0.1.2 Adapter "doorio" : 2.0.1 Adapter "ds18b20" : 1.4.1 Adapter "dwd" : 2.7.5 Adapter "dysonairpurifier": 0.9.1 Adapter "easee" : 1.0.2 Adapter "ebus" : 2.2.5 Adapter "echarts" : 0.4.11 Adapter "ecovacs-deebot": 1.1.1 Adapter "egigeozone" : 0.1.2 Adapter "ekey" : 1.1.0 Adapter "email" : 1.0.9 Adapter "emby" : 1.0.2 Adapter "energymanager" : 1.2.3 Adapter "enet" : 1.0.1 Adapter "epson_ecotank_et_2750": 0.0.5 Adapter "epson_stylus_px830": 0.2.1 Adapter "epson_xp540" : 1.0.6 Adapter "exchangerates" : 0.0.14 Adapter "fahrplan" : 1.0.7 Adapter "fakeroku" : 0.2.1 Adapter "fb-checkpresence": 1.1.4 Adapter "feiertage" : 1.0.17 Adapter "fhem" : 1.6.0 Adapter "find-my-iphone": 0.2.15 Adapter "firetv" : 1.0.0 Adapter "flot" : 1.10.6 Adapter "followthesun" : 0.3.4 Adapter "foobar2000" : 2.0.4 Adapter "fritzbox" : 0.2.1 Adapter "fritzdect" : 2.1.11 Adapter "fronius" : 1.0.5 Adapter "frontier_silicon": 0.0.10 Adapter "fuelpricemonitor": 0.2.5 Adapter "fullcalendar" : 1.1.0 Adapter "fullybrowser" : 2.0.8 Adapter "g-homa" : 0.5.3 Adapter "geofency" : 1.0.3 Adapter "go-e" : 1.0.4 Adapter "growatt" : 1.0.1 Adapter "gruenbeck" : 0.0.29 Adapter "haassohn" : 1.0.3 Adapter "habpanel" : 0.4.3 Adapter "haier" : 1.0.4 Adapter "ham" : 4.0.2 Adapter "ham-wemo" : 2.0.0 Adapter "harmony" : 1.2.2 Adapter "heatingcontrol": 2.3.2 Adapter "heos" : 1.8.0 Adapter "heytech" : 1.0.0 Adapter "hid" : 0.1.17 Adapter "history" : 1.9.12 Adapter "hm-rega" : 3.0.16 Adapter "hm-rpc" : 1.14.37 Adapter "hmip" : 1.12.1 Adapter "homeconnect" : 0.0.32 Adapter "homee" : 1.1.1 Adapter "homepilot" : 1.0.3 Adapter "hp-ilo" : 1.0.6 Adapter "hs100" : 2.0.3 Adapter "hue" : 3.5.15 Adapter "hue-extended" : 2.0.0 Adapter "i2c" : 1.2.0 Adapter "ical" : 1.7.4 Adapter "icons-addictive-flavour-png": 0.1.0 Adapter "icons-fatcow-hosting": 0.1.0 Adapter "icons-icons8" : 0.0.1 Adapter "icons-material-png": 0.1.0 Adapter "icons-material-svg": 0.1.0 Adapter "icons-mfd-png" : 1.0.2 Adapter "icons-mfd-svg" : 1.0.2 Adapter "icons-open-icon-library-png": 0.1.2 Adapter "icons-ultimate-png": 1.0.1 Adapter "influxdb" : 1.9.5 Adapter "info" : 1.7.14 , installed 1.7.14 Adapter "innogy-smarthome": 0.3.6 Adapter "iogo" : 0.6.5 Adapter "iot" : 1.8.16 Adapter "iqontrol" : 1.6.4 Adapter "jarvis" : 2.1.0 Adapter "javascript" : 5.1.3 Adapter "jeelink" : 0.1.0 Controller "js-controller" : 3.2.16 , installed 3.2.16 Adapter "kecontact" : 1.1.2 Adapter "klf200" : 1.0.1 Adapter "km200" : 1.1.6 Adapter "knmi-weather" : 1.0.0 Adapter "knx" : 1.0.45 Adapter "kodi" : 2.0.5 Adapter "kostal-piko-ba": 1.1.8 Adapter "kress" : 2.5.5 Adapter "lametric" : 1.2.0 Adapter "landroid" : 1.0.3 Adapter "lcn" : 1.0.2 Adapter "legrand-ecocompteur": 1.0.0 Adapter "letrika_comgw" : 0.0.5 Adapter "lg-ess-home" : 0.0.10 Adapter "lgtv" : 1.1.10 Adapter "lgtv-rs" : 0.1.1 Adapter "lgtv11" : 1.0.5 Adapter "lifx" : 0.1.0 Adapter "lightify" : 0.2.16 Adapter "link" : 0.5.10 Adapter "linkeddevices" : 1.4.3 Adapter "linktap" : 0.1.8 Adapter "linux-control" : 1.1.2 Adapter "logparser" : 1.1.0 Adapter "lovelace" : 1.0.16 Adapter "loxone" : 2.1.0 Adapter "luftdaten" : 1.0.2 Adapter "lupusec" : 1.3.4 Adapter "luxtronik1" : 0.3.1 Adapter "material" : 0.13.9 Adapter "maxcube" : 1.0.3 Adapter "maxcul" : 1.3.1 Adapter "mbus" : 2.3.4 Adapter "mclighting" : 0.1.2 Adapter "megad" : 1.2.1 Adapter "megadd" : 0.2.0 Adapter "megaesp" : 0.1.0 Adapter "melcloud" : 1.1.4 Adapter "mercedesme" : 0.0.50 Adapter "mercury" : 0.1.4 Adapter "meross" : 1.6.2 Adapter "meteoalarm" : 1.2.0 Adapter "midea" : 0.0.6 Adapter "miele" : 0.1.5 Adapter "mielecloudservice": 4.2.0 Adapter "mihome" : 1.3.7 Adapter "mihome-lamp" : 1.1.0 Adapter "mihome-plug" : 0.2.1 Adapter "mihome-vacuum" : 2.1.1 Adapter "mikrotik" : 1.0.16 Adapter "milight" : 0.3.6 Adapter "milight-smart-light": 1.2.0 Adapter "minuvis" : 1.4.0 Adapter "mobile" : 1.0.1 Adapter "modbus" : 3.2.6 Adapter "moma" : 1.2.8 Adapter "mpd" : 1.0.6 Adapter "mqtt" : 2.4.0 Adapter "mqtt-client" : 1.3.1 Adapter "musiccast" : 0.1.5 Adapter "mydlink" : 1.1.7 Adapter "mysensors" : 2.0.1 Adapter "nanoleaf-lightpanels": 1.2.0 Adapter "net-tools" : 0.1.2 Adapter "netatmo" : 1.3.3 Adapter "netatmo-crawler": 0.4.1 Adapter "nibeuplink" : 0.4.0 Adapter "nina" : 0.0.24 Adapter "node-red" : 2.3.0 Adapter "nuki" : 1.4.3 Adapter "nuki-extended" : 2.3.0 Adapter "nut" : 1.5.0 Adapter "octoprint" : 1.0.8 Adapter "odl" : 1.1.4 Adapter "oilfox" : 0.0.5 Adapter "omnicomm-lls" : 0.0.7 Adapter "onkyo" : 2.0.5 Adapter "onvif" : 0.4.4 Adapter "openhab" : 1.1.0 Adapter "openligadb" : 1.1.0 Adapter "openweathermap": 0.1.0 Adapter "opi" : 0.1.1 Adapter "oppoplayer" : 0.2.4 Adapter "owfs" : 0.6.4 Adapter "owntracks" : 1.0.0 Adapter "panasonic-viera": 1.0.2 Adapter "parser" : 1.0.7 Adapter "paw" : 0.0.7 Adapter "pegelalarm" : 1.2.0 Adapter "phantomjs" : 1.1.2 Adapter "pi-hole" : 1.3.1 Adapter "piface" : 1.0.0 Adapter "pimatic" : 0.3.0 Adapter "ping" : 1.4.12 Adapter "places" : 1.0.0 Adapter "plenticore" : 2.1.6 Adapter "plex" : 0.8.11 Adapter "plexconnect" : 0.0.7 Adapter "pollenflug" : 1.0.6 Adapter "proxmox" : 1.3.3 Adapter "proxy" : 1.2.2 Adapter "pushbullet" : 0.0.11 Adapter "pushover" : 2.0.3 Adapter "pushsafer" : 1.0.3 Adapter "radar2" : 1.0.9 Adapter "radiohead" : 1.1.1 Adapter "rflink" : 2.1.6 Adapter "rickshaw" : 1.0.0 Adapter "ring" : 1.1.3 Adapter "robonect" : 0.1.3 Adapter "roomba" : 1.1.1 Adapter "rpi2" : 1.2.0 Adapter "s7" : 1.2.5 Adapter "sainlogic" : 0.6.6 Adapter "samsung" : 0.2.9 Adapter "sanext" : 0.0.5 Adapter "sayit" : 1.12.2 Adapter "sbfspot" : 4.0.5 Adapter "scenes" : 2.3.6 Adapter "schoolfree" : 1.0.0 Adapter "schwoerer-ventcube": 1.4.1 Adapter "seq" : 0.2.10 Adapter "shelly" : 4.0.7 Adapter "shuttercontrol": 1.2.0 Adapter "sia" : 1.0.4 Adapter "siegenia" : 1.1.0 Adapter "simple-api" : 2.6.1 Adapter "smappee" : 0.2.4 Adapter "smartcontrol" : 1.2.1 Adapter "smartgarden" : 1.0.5 Adapter "smartmeter" : 3.2.1 Adapter "snips" : 1.5.1 Adapter "snmp" : 0.5.0 Adapter "socketio" : 3.1.4 Adapter "solarlog" : 2.1.2 Adapter "solarviewdatareader": 1.0.2 Adapter "solarwetter" : 1.0.0 Adapter "sonnen" : 1.7.3 Adapter "sonoff" : 2.4.0 Adapter "sonos" : 2.1.1 Adapter "sony-bravia" : 1.0.1 Adapter "spotify-premium": 1.0.0 Adapter "sprinklecontrol": 0.1.7 Adapter "sql" : 1.15.7 Adapter "squeezebox" : 1.0.0 Adapter "squeezeboxrpc" : 1.3.4 Adapter "starline" : 1.1.3 Adapter "statistics" : 1.0.4 Adapter "stiebel-isg" : 1.6.0 Adapter "sunnyportal" : 0.1.5 Adapter "swiss-weather-api": 0.3.2 Adapter "synology" : 1.0.0 Adapter "systeminfo" : 0.3.1 Adapter "tahoma" : 0.3.2 Adapter "tankerkoenig" : 2.0.5 Adapter "telegram" : 1.8.1 Adapter "terminal" : 0.1.2 Adapter "tesla-motors" : 0.4.2 Adapter "text2command" : 2.0.7 Adapter "tinker" : 1.1.0 Adapter "tr-064" : 4.2.12 Adapter "traccar" : 0.0.9 Adapter "tradfri" : 2.7.2 Adapter "trashschedule" : 1.1.1 Adapter "tunnelbroker-endpoint-updater": 0.0.1 Adapter "tuya" : 3.6.2 Adapter "tvprogram" : 1.1.0 Adapter "tvspielfilm" : 1.0.4 Adapter "unifi" : 0.5.8 Adapter "upnp" : 1.0.17 Adapter "vaillant" : 0.0.11 Adapter "valloxmv" : 1.1.2 Adapter "vcard" : 0.0.9 Adapter "velux" : 0.0.7 Adapter "viessmann" : 1.3.4 Adapter "virtualpowermeter": 1.4.2 Adapter "vis" : 1.3.8 Adapter "vis-bars" : 0.1.4 Adapter "vis-canvas-gauges": 0.1.5 Adapter "vis-colorpicker": 1.2.0 Adapter "vis-fancyswitch": 1.1.0 Adapter "vis-google-fonts": 0.1.0 Adapter "vis-history" : 1.0.0 Adapter "vis-hqwidgets" : 1.1.7 Adapter "vis-icontwo" : 0.69.0 Adapter "vis-inventwo" : 2.8.3 Adapter "vis-jqui-mfd" : 1.0.12 Adapter "vis-justgage" : 1.0.2 Adapter "vis-keyboard" : 0.0.2 Adapter "vis-lcars" : 1.0.4 Adapter "vis-map" : 1.0.4 Adapter "vis-material-advanced": 1.7.0 Adapter "vis-metro" : 1.1.2 Adapter "vis-players" : 0.1.6 Adapter "vis-plumb" : 1.0.2 Adapter "vis-rgraph" : 0.0.2 Adapter "vis-timeandweather": 1.1.7 Adapter "vis-weather" : 2.5.3 Adapter "volumio" : 0.1.2 Adapter "volvo" : 0.0.3 Adapter "vr200" : 1.0.0 Adapter "vw-connect" : 0.0.30 Adapter "weatherunderground": 3.3.0 Adapter "web" : 3.4.0 Adapter "weishaupt-wem" : 0.0.9 Adapter "whatsapp-cmb" : 0.1.6 Adapter "wiffi-wz" : 2.2.0 Adapter "wifilight" : 1.1.0 Adapter "windows-control": 0.1.5 Adapter "wled" : 0.5.6 Adapter "wm-bus" : 0.1.12 Adapter "wolf" : 1.2.1 Adapter "worx" : 1.3.6 Adapter "xbox" : 0.7.7 Adapter "xs1" : 1.0.2 Adapter "yahka" : 0.12.0 Adapter "yamaha" : 0.4.0 Adapter "yeelight-2" : 1.0.3 Adapter "youtube" : 1.0.3 Adapter "yr" : 2.0.3 Adapter "zigbee" : 1.5.6 Adapter "zont" : 0.5.3 Adapter "zwave2" : 1.9.3 -
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
Gibt es hierfür...
Fixing "sudo-bug" by replacing sudo in iobroker with gosu... Done.
...einen einfachen Fix?Warum willst du einen Fix fixen? Das ist nur eine Info dass im Container sudo durch gosu ersetzt wurde
-
@fastfoot sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
Gibt es hierfür...
Fixing "sudo-bug" by replacing sudo in iobroker with gosu... Done.
...einen einfachen Fix?Warum willst du einen Fix fixen? Das ist nur eine Info dass im Container sudo durch gosu ersetzt wurde
Ich hatte dass so aufgefasst, als wenn wegen 'Berechtigungen' das Backup ungenutzt bleibt.
Ich will doch nur, dass mein Backup beim Container erstellen 'aktiviert' wird.
-
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
Ich will doch nur, dass mein Backup beim Container erstellen 'aktiviert' wird.
Dazu muss das file aber in /opt/iobroker liegen, nicht in /opt/iobroker/backup. Der gesamte Ordner muss dazu auch leer sein(außer dem Backupfile).
Du kannst es jetzt aber auch so einspielen:
- pkill -u iobroker
- iobroker restore 0 (oder iobroker restore backupfilename)
- Neustart des Containers und Warten bis Adapter installiert wurden
-
@fastfoot sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
Ich will doch nur, dass mein Backup beim Container erstellen 'aktiviert' wird.
Dazu muss das file aber in /opt/iobroker liegen, nicht in /opt/iobroker/backup. Der gesamte Ordner muss dazu auch leer sein(außer dem Backupfile).
Du kannst es jetzt aber auch so einspielen:
- pkill -u iobroker
- iobroker restore 0 (oder iobroker restore backupfilename)
- Neustart des Containers und Warten bis Adapter installiert wurden
Das scheint weder in der Container Console, noch in Putty zu funktionieren.
Das Backup hatte ich im Host Pfad abgelegt.
/opt/iobroker/backups/ -
SSH erkennt verständlicher weise den Befehl 'iobroker' nicht.
In der Container Console erreiche in den Host Pfad nicht.
-
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
SSH erkennt verständlicher weise den Befehl 'iobroker' nicht.
In der Container Console erreiche in den Host Pfad nicht.
was heisst denn scheint? wenn dein Backup dort liegt dann funktioniert es genau wie beschrieben, natürlich von der Containerkonsole aus
-
Dazu muss das file aber in /opt/iobroker liegen, nicht in /opt/iobroker/backup. Der gesamte Ordner muss dazu auch leer sein(außer dem Backupfile).
Ich hab vor dem Container Neustart das Backup in den iobroker Ordner verschobe und den backups Ordner gelöscht.
Das Ergebnis ist leider das selbe.
Das Backup läuft nicht.----- Welcome to your ioBroker-container! ----- ----- Startupscript is now running. ----- ----- Please be patient! ----- ------------------------------------------------------------ ------------------------------------------------------------ ----- Debugging information ----- ----- ----- ----- System ----- ----- arch: armv7l ----- ----- ----- ----- Versions ----- ----- image: v5.1.0 ----- ----- node: v12.22.1 ----- ----- npm: 6.14.12 ----- ----- ----- ----- ENV ----- ----- PACKAGES: nano ----- ----- SETGID: 1000 ----- ----- SETUID: 1000 ----- ----- USBDEVICES: /dev/serial/by-id/ ----- ----- ZWAVE: false ----- ------------------------------------------------------------ ------------------------------------------------------------ ----- Step 1 of 5: Preparing container ----- ------------------------------------------------------------ Installing additional packages is set by ENV. The following packages will be installed: nano... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 1.) debconf: falling back to frontend: Readline Selecting previously unselected package nano. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 25575 files and directories currently installed.) Preparing to unpack .../archives/nano_3.2-3_armhf.deb ... Unpacking nano (3.2-3) ... Setting up nano (3.2-3) ... update-alternatives: using /bin/nano to provide /usr/bin/editor (editor) in auto mode update-alternatives: warning: skip creation of /usr/share/man/man1/editor.1.gz because associated file /usr/share/man/man1/nano.1.gz (of link group editor) doesn't exist update-alternatives: using /bin/nano to provide /usr/bin/pico (pico) in auto mode update-alternatives: warning: skip creation of /usr/share/man/man1/pico.1.gz because associated file /usr/share/man/man1/nano.1.gz (of link group pico) doesn't exist 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 folder permissions (This might take a while! Please be patient!)... Done. Fixing "sudo-bug" by replacing sudo in iobroker with gosu... Done. Hostname in ioBroker does not match the hostname of this container. Updating hostname to RasPi4b... The host for instance "system.adapter.admin.0" was changed from "c9b7b12a8335" to "RasPi4b". The host for instance "system.adapter.discovery.0" was changed from "c9b7b12a8335" to "RasPi4b". The host for instance "system.adapter.info.0" was changed from "c9b7b12a8335" to "RasPi4b". Done. ------------------------------------------------------------ ----- 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 take a look at readme.md on Github! Usb-device-support is activated by ENV. Setting permissions for /dev/serial/by-id/... Done. ------------------------------------------------------------ ----- Step 5 of 5: ioBroker startup ----- ------------------------------------------------------------ Starting ioBroker... host.RasPi4b check instance "system.adapter.admin.0" for host "RasPi4b" host.RasPi4b check instance "system.adapter.discovery.0" for host "RasPi4b" host.RasPi4b check instance "system.adapter.info.0" for host "RasPi4b" Send diag info: {"uuid":"ab265f4a-67f9-a46a-c0b2-61e4b95cefe5","language":"","country":"","hosts":[{"version":"3.2.16","platform":"Javascript/Node.js","type":"linux"}],"node":"v12.22.1","arch":"arm","adapters":{"admin":{"version":"4.2.1","platform":"Javascript/Node.js"},"discovery":{"version":"2.6.1","platform":"Javascript/Node.js"},"info":{"version":"1.7.14","platform":"Javascript/Node.js"}},"statesType":"file","objectsType":"file","model":"ARMv7 Processor rev 3 (v7l)","cpus":4,"mem":4013191168,"ostype":"Linux","city":""} hash changed or no sources cached => force download of new sources ls: cannot access '/dev/disk/by-id/': No such file or directory ls: cannot access '/dev/disk/by-id/': No such file or directory Send diag info: {"uuid":"ab265f4a-67f9-a46a-c0b2-61e4b95cefe5","language":"","country":"","hosts":[{"version":"3.2.16","platform":"Javascript/Node.js","type":"linux"}],"node":"v12.22.1","arch":"arm","adapters":{"admin":{"version":"4.2.1","platform":"Javascript/Node.js"},"discovery":{"version":"2.6.1","platform":"Javascript/Node.js"},"info":{"version":"1.7.14","platform":"Javascript/Node.js"}},"statesType":"file","objectsType":"file","model":"ARMv7 Processor rev 3 (v7l)","cpus":4,"mem":4013191168,"ostype":"Linux","city":""} Send diag info: {"uuid":"ab265f4a-67f9-a46a-c0b2-61e4b95cefe5","language":"de","country":"","hosts":[{"version":"3.2.16","platform":"Javascript/Node.js","type":"linux"}],"node":"v12.22.1","arch":"arm","adapters":{"admin":{"version":"4.2.1","platform":"Javascript/Node.js"},"discovery":{"version":"2.6.1","platform":"Javascript/Node.js"},"info":{"version":"1.7.14","platform":"Javascript/Node.js"}},"statesType":"file","objectsType":"file","model":"ARMv7 Processor rev 3 (v7l)","cpus":4,"mem":4013191168,"ostype":"Linux","city":""} Send diag info: {"uuid":"ab265f4a-67f9-a46a-c0b2-61e4b95cefe5","language":"de","country":"","hosts":[{"version":"3.2.16","platform":"Javascript/Node.js","type":"linux"}],"node":"v12.22.1","arch":"arm","adapters":{"admin":{"version":"4.2.1","platform":"Javascript/Node.js"},"discovery":{"version":"2.6.1","platform":"Javascript/Node.js"},"info":{"version":"1.7.14","platform":"Javascript/Node.js"}},"statesType":"file","objectsType":"file","model":"ARMv7 Processor rev 3 (v7l)","cpus":4,"mem":4013191168,"ostype":"Linux","city":""} Send diag info: {"uuid":"ab265f4a-67f9-a46a-c0b2-61e4b95cefe5","language":"de","country":"","hosts":[{"version":"3.2.16","platform":"Javascript/Node.js","type":"linux"}],"node":"v12.22.1","arch":"arm","adapters":{"admin":{"version":"4.2.1","platform":"Javascript/Node.js"},"discovery":{"version":"2.6.1","platform":"Javascript/Node.js"},"info":{"version":"1.7.14","platform":"Javascript/Node.js"}},"statesType":"file","objectsType":"file","model":"ARMv7 Processor rev 3 (v7l)","cpus":4,"mem":4013191168,"ostype":"Linux","city":""} -
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
Das Backup hatte ich im Host Pfad abgelegt.
/opt/iobroker/backups/Das ist aber der Containerpfad, bzw. muss es sein. Den Pfad kannst du ja auch mappen
volumes: - /opt/iobroker:/var/lib/docker/volumes/iobrokerdata - /opt/iobroker/backups:/var/lib/docker/volumes/iobrokerdata/backups -
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
Ich hab vor dem Container Neustart das Backup in den iobroker Ordner verschobe und den backups Ordner gelöscht.
Das funktioniert nur beim erstmaligen Start des Containers, danach nie wieder
-
In der Container Console erreiche in den Host Pfad nicht.
was heisst denn scheint? wenn dein Backup dort liegt dann funktioniert es genau wie beschrieben, natürlich von der Containerkonsole aus
root@RasPi4b:/opt/iobroker# ls INSTALLER_INFO.txt iob iobroker iobroker.bak iobroker-data log node_modules package.json package-lock.json reinstall.js root@RasPi4b:/opt/iobroker# pkill -u iobroker root@RasPi4b:/opt/iobroker# iobroker restore 0 No matching backup found host.RasPi4b Cannot find /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../../../backups/_backupiobroker.tar.gz root@RasPi4b:/opt/iobroker# ^C root@RasPi4b:/opt/iobroker# -
@fastfoot sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
Ich hab vor dem Container Neustart das Backup in den iobroker Ordner verschobe und den backups Ordner gelöscht.
Das funktioniert nur beim erstmaligen Start des Containers, danach nie wieder
Ich hatte den Container Removed
Und einen neuen erstellt !?
-
ls /opt/iobroker/backups -
@fastfoot sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
ls /opt/iobroker/backups
root@RasPi4b:/opt/iobroker# ls /opt/iobroker/backups ls: cannot access '/opt/iobroker/backups': No such file or directory root@RasPi4b:/opt/iobroker# -
@divedancer sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:
Ich hatte den Container Removed
Und einen neuen erstellt !?/var/lib/docker/volumes/iobrokerdata muss dann leer sein! Das Backupfile dann da rein und starten. Oder einen Backupordner zusätzlich mappen und anschliessend wie gezeigt manuell
-
Das ist wohl zu hoch für mich
root@RasPi4b:/opt/iobroker# ls INSTALLER_INFO.txt iob iobroker iobroker.bak iobroker-data log node_modules package.json package-lock.json reinstall.js root@RasPi4b:/opt/iobroker# cd root@RasPi4b:~# cd .. root@RasPi4b:/# ls bin boot dev etc home lib media mnt opt proc root run sbin srv sys tmp usr var root@RasPi4b:/# cd var root@RasPi4b:/var# cd lib root@RasPi4b:/var/lib# cd docker root@RasPi4b:/var/lib/docker# cd volumes root@RasPi4b:/var/lib/docker/volumes# ls iobrokerdata root@RasPi4b:/var/lib/docker/volumes# cd iobrokerdata/ root@RasPi4b:/var/lib/docker/volumes/iobrokerdata# ls backups iobroker_2021_06_07-02_46_10_Pi4_a_backupiobroker.tar.gz root@RasPi4b:/var/lib/docker/volumes/iobrokerdata# cd backups root@RasPi4b:/var/lib/docker/volumes/iobrokerdata/backups# ls iobroker_2021_06_07-02_46_10_Pi4_a_backupiobroker.tar.gz root@RasPi4b:/var/lib/docker/volumes/iobrokerdata/backups# pkill -u iobroker root@RasPi4b:/var/lib/docker/volumes/iobrokerdata/backups# iobroker restore 0 No matching backup found host.RasPi4b Cannot find /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../../../backups/_backupiobroker.tar.gz root@RasPi4b:/var/lib/docker/volumes/iobrokerdata/backups# -
/var/lib/docker/volumes/iobrokerdata muss dann leer sein! Das Backupfile dann da rein und starten. Oder einen Backupordner zusätzlich mappen und anschliessend wie gezeigt manuell
das Backup in deinen Pfad, wenn der Ordner gelöscht und neu erstellt wurde?
Oder im Anschluss muss das Backup wie gehabt im Pfad: /opt/iobroker/
liegen???
