Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Einsteigerfragen
  4. Installation
  5. ioBroker - DockerContainer MacOS Ports nicht erreichbar

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    14
    1
    377

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    605

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    1.8k

ioBroker - DockerContainer MacOS Ports nicht erreichbar

Geplant Angeheftet Gesperrt Verschoben Installation
7 Beiträge 2 Kommentatoren 616 Aufrufe 2 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • B Offline
    B Offline
    BennyBO
    schrieb am zuletzt editiert von
    #1

    Hallo zusammen, ich hoffe jemand kann weiterhelfen, die Suche hat mich leider nicht wirklich weiter gebracht....

    Wollte endlich mal mein Home smart machen und versuche mich gerade mit ioBroker....

    Leider hab ich das Problem das zwar die Admin Seite (localhost bzw. / localhost:80) erreichbar ist, aber die Adminseite z.B. über (localhost:8081) und vis localhost:8021 oder andere Seiten (HabPanel localhost:8084) leider nicht.... Hat jemand eine Idee ob es an der Config des ioBrokers liegt oder vielleicht ist es auch ein Docker Problem ?

    Vielen Dank vorab für Eure Mithilfe!!!!

    Meine Config:
    MacOS Monterey v. 12.5.1
    Docker Desktop 4.12.0
    ioBroker Container : buanet/iobroker:latest (v6.2.20)
    ---- System -----
    ----- arch: aarch64 -----
    ----- hostname: bf64bf220169 -----


    ----- Docker-Image -----
    ----- image: v7.0.1 -----
    ----- build: 2022-07-05T18:51:52+00:00 -----


    ----- Versions -----
    ----- node: v16.15.1 -----
    ----- npm: 8.11.0 -----


    ----- ENV -----
    ----- SETGID: 1000 -----
    ----- SETUID: 1000 -----

    R 1 Antwort Letzte Antwort
    0
    • B BennyBO

      Hallo zusammen, ich hoffe jemand kann weiterhelfen, die Suche hat mich leider nicht wirklich weiter gebracht....

      Wollte endlich mal mein Home smart machen und versuche mich gerade mit ioBroker....

      Leider hab ich das Problem das zwar die Admin Seite (localhost bzw. / localhost:80) erreichbar ist, aber die Adminseite z.B. über (localhost:8081) und vis localhost:8021 oder andere Seiten (HabPanel localhost:8084) leider nicht.... Hat jemand eine Idee ob es an der Config des ioBrokers liegt oder vielleicht ist es auch ein Docker Problem ?

      Vielen Dank vorab für Eure Mithilfe!!!!

      Meine Config:
      MacOS Monterey v. 12.5.1
      Docker Desktop 4.12.0
      ioBroker Container : buanet/iobroker:latest (v6.2.20)
      ---- System -----
      ----- arch: aarch64 -----
      ----- hostname: bf64bf220169 -----


      ----- Docker-Image -----
      ----- image: v7.0.1 -----
      ----- build: 2022-07-05T18:51:52+00:00 -----


      ----- Versions -----
      ----- node: v16.15.1 -----
      ----- npm: 8.11.0 -----


      ----- ENV -----
      ----- SETGID: 1000 -----
      ----- SETUID: 1000 -----

      R Offline
      R Offline
      rewenode
      schrieb am zuletzt editiert von
      #2

      @bennybo Mit welchen Optionen hast du denn den Container gestartet? Wie sehen die die Port-Mappings aus?

      Gruß
      Reiner

      B 1 Antwort Letzte Antwort
      0
      • R rewenode

        @bennybo Mit welchen Optionen hast du denn den Container gestartet? Wie sehen die die Port-Mappings aus?

        Gruß
        Reiner

        B Offline
        B Offline
        BennyBO
        schrieb am zuletzt editiert von BennyBO
        #3

        @rewenode Bildschirmfoto 2022-09-09 um 10.44.57.png

        Ich hatte das Ganze auch schon mal mit Port 8081 gestartet, dann kommt man gar nicht zur Admin Seite! Nur als Info, wenn ich im Web.Adapter den Port auf 80 umstelle bekomme ich bei den Seite VIS oder HabPanel : Cannot GET /vis/index.html bzw. selbe Meldung für HabPanel mit entsprechend : Cannot GET /habpanel/index.html

        R 1 Antwort Letzte Antwort
        0
        • B BennyBO

          @rewenode Bildschirmfoto 2022-09-09 um 10.44.57.png

          Ich hatte das Ganze auch schon mal mit Port 8081 gestartet, dann kommt man gar nicht zur Admin Seite! Nur als Info, wenn ich im Web.Adapter den Port auf 80 umstelle bekomme ich bei den Seite VIS oder HabPanel : Cannot GET /vis/index.html bzw. selbe Meldung für HabPanel mit entsprechend : Cannot GET /habpanel/index.html

          R Offline
          R Offline
          rewenode
          schrieb am zuletzt editiert von rewenode
          #4

          @bennybo Ich kenne zwar das Programm nicht, das der Screenshot zeigt, aber wie es aussieht, hast du bis auf Port 80 keine weiteren Ports gemappt.
          Wie erstellst du denn den Container?
          Da sollten dann die entsprechenden Ports gemappt werden

              ports:
                - "1880:1880"  #node-red
                - "2001:2001"  #homematic
                - "8081:8081"  #iobroker admin
                - "8282:8282"  #flot
                - "8087:8087"  #simple API
                - "8088:8088"  #terminal 
                - "8084:8084"  #socketIO
                - "6666:6666/udp"  #tuya Adapter
                - "8887:8887/udp"  #tuya proxy
                - "8887:8887/tcp"
                - "8889:8889/udp"  #tuya proxy-web
                - "8889:8889/tcp"  
                - "9900:9900" #proxy       
          #      - "1883:1883"  #mqtt
          
          

          Siehe hier

          Gruß
          Reiner

          B 1 Antwort Letzte Antwort
          0
          • R rewenode

            @bennybo Ich kenne zwar das Programm nicht, das der Screenshot zeigt, aber wie es aussieht, hast du bis auf Port 80 keine weiteren Ports gemappt.
            Wie erstellst du denn den Container?
            Da sollten dann die entsprechenden Ports gemappt werden

                ports:
                  - "1880:1880"  #node-red
                  - "2001:2001"  #homematic
                  - "8081:8081"  #iobroker admin
                  - "8282:8282"  #flot
                  - "8087:8087"  #simple API
                  - "8088:8088"  #terminal 
                  - "8084:8084"  #socketIO
                  - "6666:6666/udp"  #tuya Adapter
                  - "8887:8887/udp"  #tuya proxy
                  - "8887:8887/tcp"
                  - "8889:8889/udp"  #tuya proxy-web
                  - "8889:8889/tcp"  
                  - "9900:9900" #proxy       
            #      - "1883:1883"  #mqtt
            
            

            Siehe hier

            Gruß
            Reiner

            B Offline
            B Offline
            BennyBO
            schrieb am zuletzt editiert von
            #5

            @rewenode Erstmal Danke für Deine Antworten, wenn ich das so mache wie im Link macht er einen neuen Container (Neuinstallation) der dann zwar unter Port 8081 erreichbar ist, die Problematik bleibt beim Rest aber die Gleiche, vielleicht schaue ich mal nach Befehlen für das Port Mapping für Docker Desktop, hab damit nie wirklich gearbeitet, daher bin ich in dieser Angelegenheit leider nicht firm, oder hast Du noch eine Idee ?

            Hier das was von Docker ausgeführt wurde:

            docker run -p 8081:8081 --name iobroker1 -v iobrokerdata:/opt/iobroker1 buanet/iobroker:latest


            ------------------------- 2022-09-09 10:56:06 -------------------------


            ----- Welcome to your ioBroker-container! -----
            ----- Startupscript is now running. -----
            ----- Please be patient! -----


            ----- Debugging information -----


            ----- System -----
            ----- arch: aarch64 -----
            ----- hostname: 38224fdc84de -----


            ----- Docker-Image -----
            ----- image: v7.0.1 -----
            ----- build: 2022-07-05T18:51:52+00:00 -----


            ----- Versions -----
            ----- node: v16.15.1 -----
            ----- npm: 8.11.0 -----


            ----- ENV -----
            ----- SETGID: 1000 -----
            ----- SETUID: 1000 -----


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

            Updating Linux packages on first run...
            dpkg-preconfigure: unable to re-open stdin:
            (Reading database ... 29325 files and directories currently installed.)
            Preparing to unpack .../base-files_11.1+deb11u4_arm64.deb ...
            Unpacking base-files (11.1+deb11u4) over (11.1+deb11u3) ...
            Setting up base-files (11.1+deb11u4) ...
            Installing new version of config file /etc/debian_version ...
            (Reading database ... 29325 files and directories currently installed.)
            Preparing to unpack .../bash_5.1-2+deb11u1_arm64.deb ...
            update-alternatives: warning: alternative /usr/share/man/man7/bash-builtins.7.gz (part of link group builtins.7.gz) doesn't exist; removing from list of alternatives
            update-alternatives: warning: /etc/alternatives/builtins.7.gz is dangling; it will be updated with best choice
            Unpacking bash (5.1-2+deb11u1) over (5.1-2+b3) ...
            Setting up bash (5.1-2+deb11u1) ...
            update-alternatives: error: alternative path /usr/share/man/man7/bash-builtins.7.gz doesn't exist
            (Reading database ... 29324 files and directories currently installed.)
            Preparing to unpack .../dpkg_1.20.11_arm64.deb ...
            Unpacking dpkg (1.20.11) over (1.20.10) ...
            Setting up dpkg (1.20.11) ...
            (Reading database ... 29324 files and directories currently installed.)
            Preparing to unpack .../libgnutls30_3.7.1-5+deb11u2_arm64.deb ...
            Unpacking libgnutls30:arm64 (3.7.1-5+deb11u2) over (3.7.1-5) ...
            Setting up libgnutls30:arm64 (3.7.1-5+deb11u2) ...
            (Reading database ... 29324 files and directories currently installed.)
            Preparing to unpack .../libwbclient0_2%3a4.13.13+dfsg-1~deb11u5_arm64.deb ...
            Unpacking libwbclient0:arm64 (2:4.13.13+dfsg-1~deb11u5) over (2:4.13.13+dfsg-1~deb11u3) ...
            Preparing to unpack .../libssl1.1_1.1.1n-0+deb11u3_arm64.deb ...
            Unpacking libssl1.1:arm64 (1.1.1n-0+deb11u3) over (1.1.1n-0+deb11u2) ...
            Setting up libssl1.1:arm64 (1.1.1n-0+deb11u3) ...
            (Reading database ... 29324 files and directories currently installed.)
            Preparing to unpack .../libtirpc-common_1.3.1-1+deb11u1_all.deb ...
            Unpacking libtirpc-common (1.3.1-1+deb11u1) over (1.3.1-1) ...
            Setting up libtirpc-common (1.3.1-1+deb11u1) ...
            (Reading database ... 29324 files and directories currently installed.)
            Preparing to unpack .../libtirpc-dev_1.3.1-1+deb11u1_arm64.deb ...
            Unpacking libtirpc-dev:arm64 (1.3.1-1+deb11u1) over (1.3.1-1) ...
            Preparing to unpack .../libtirpc3_1.3.1-1+deb11u1_arm64.deb ...
            Unpacking libtirpc3:arm64 (1.3.1-1+deb11u1) over (1.3.1-1) ...
            Setting up libtirpc3:arm64 (1.3.1-1+deb11u1) ...
            (Reading database ... 29324 files and directories currently installed.)
            Preparing to unpack .../zlib1g-dev_1%3a1.2.11.dfsg-2+deb11u2_arm64.deb ...
            Unpacking zlib1g-dev:arm64 (1:1.2.11.dfsg-2+deb11u2) over (1:1.2.11.dfsg-2+deb11u1) ...
            Preparing to unpack .../zlib1g_1%3a1.2.11.dfsg-2+deb11u2_arm64.deb ...
            Unpacking zlib1g:arm64 (1:1.2.11.dfsg-2+deb11u2) over (1:1.2.11.dfsg-2+deb11u1) ...
            Setting up zlib1g:arm64 (1:1.2.11.dfsg-2+deb11u2) ...
            (Reading database ... 29324 files and directories currently installed.)
            Preparing to unpack .../00-tzdata_2021a-1+deb11u5_all.deb ...
            Unpacking tzdata (2021a-1+deb11u5) over (2021a-1+deb11u4) ...
            Preparing to unpack .../01-curl_7.74.0-1.3+deb11u2_arm64.deb ...
            Unpacking curl (7.74.0-1.3+deb11u2) over (7.74.0-1.3+deb11u1) ...
            Preparing to unpack .../02-libcurl4_7.74.0-1.3+deb11u2_arm64.deb ...
            Unpacking libcurl4:arm64 (7.74.0-1.3+deb11u2) over (7.74.0-1.3+deb11u1) ...
            Preparing to unpack .../03-distro-info-data_0.51+deb11u2_all.deb ...
            Unpacking distro-info-data (0.51+deb11u2) over (0.51+deb11u1) ...
            Preparing to unpack .../04-dpkg-dev_1.20.11_all.deb ...
            Unpacking dpkg-dev (1.20.11) over (1.20.10) ...
            Preparing to unpack .../05-libdpkg-perl_1.20.11_all.deb ...
            Unpacking libdpkg-perl (1.20.11) over (1.20.10) ...
            Preparing to unpack .../06-libcurl3-gnutls_7.74.0-1.3+deb11u2_arm64.deb ...
            Unpacking libcurl3-gnutls:arm64 (7.74.0-1.3+deb11u2) over (7.74.0-1.3+deb11u1) ...
            Preparing to unpack .../07-libfreetype-dev_2.10.4+dfsg-1+deb11u1_arm64.deb ...
            Unpacking libfreetype-dev:arm64 (2.10.4+dfsg-1+deb11u1) over (2.10.4+dfsg-1) ...
            Preparing to unpack .../08-libfreetype6-dev_2.10.4+dfsg-1+deb11u1_arm64.deb ...
            Unpacking libfreetype6-dev:arm64 (2.10.4+dfsg-1+deb11u1) over (2.10.4+dfsg-1) ...
            Preparing to unpack .../09-libfreetype6_2.10.4+dfsg-1+deb11u1_arm64.deb ...
            Unpacking libfreetype6:arm64 (2.10.4+dfsg-1+deb11u1) over (2.10.4+dfsg-1) ...
            Preparing to unpack .../10-libfribidi-dev_1.0.8-2+deb11u1_arm64.deb ...
            Unpacking libfribidi-dev:arm64 (1.0.8-2+deb11u1) over (1.0.8-2) ...
            Preparing to unpack .../11-libfribidi0_1.0.8-2+deb11u1_arm64.deb ...
            Unpacking libfribidi0:arm64 (1.0.8-2+deb11u1) over (1.0.8-2) ...
            Preparing to unpack .../12-linux-libc-dev_5.10.136-1_arm64.deb ...
            Unpacking linux-libc-dev:arm64 (5.10.136-1) over (5.10.120-1) ...
            Preparing to unpack .../13-nodejs_16.17.0-deb-1nodesource1_arm64.deb ...
            Unpacking nodejs (16.17.0-deb-1nodesource1) over (16.15.1-deb-1nodesource1) ...
            Preparing to unpack .../14-unzip_6.0-26+deb11u1_arm64.deb ...
            Unpacking unzip (6.0-26+deb11u1) over (6.0-26) ...
            Setting up distro-info-data (0.51+deb11u2) ...
            Setting up unzip (6.0-26+deb11u1) ...
            Setting up linux-libc-dev:arm64 (5.10.136-1) ...
            Setting up libcurl3-gnutls:arm64 (7.74.0-1.3+deb11u2) ...
            Setting up nodejs (16.17.0-deb-1nodesource1) ...
            Setting up libwbclient0:arm64 (2:4.13.13+dfsg-1~deb11u5) ...
            Setting up tzdata (2021a-1+deb11u5) ...

            Current default time zone: 'Etc/UTC'
            Local time is now: Fri Sep 9 08:56:25 UTC 2022.
            Universal Time is now: Fri Sep 9 08:56:25 UTC 2022.
            Run 'dpkg-reconfigure tzdata' if you wish to change it.

            Setting up libtirpc-dev:arm64 (1.3.1-1+deb11u1) ...
            Setting up libfreetype6:arm64 (2.10.4+dfsg-1+deb11u1) ...
            Setting up libfribidi0:arm64 (1.0.8-2+deb11u1) ...
            Setting up libdpkg-perl (1.20.11) ...
            Setting up zlib1g-dev:arm64 (1:1.2.11.dfsg-2+deb11u2) ...
            Setting up libcurl4:arm64 (7.74.0-1.3+deb11u2) ...
            Setting up curl (7.74.0-1.3+deb11u2) ...
            Setting up libfribidi-dev:arm64 (1.0.8-2+deb11u1) ...
            Setting up dpkg-dev (1.20.11) ...
            Setting up libfreetype-dev:arm64 (2.10.4+dfsg-1+deb11u1) ...
            Setting up libfreetype6-dev:arm64 (2.10.4+dfsg-1+deb11u1) ...
            Processing triggers for libc-bin (2.31-13+deb11u3) ...
            Reading package lists...
            Building dependency tree...
            Reading state information...
            Reading package lists...
            Building dependency tree...
            Reading state information...
            0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
            Done.

            Registering maintenance script as command... Done.

            Installing additional packages is set by ENV.
            Checking the following Packages: ...
            Reading package lists...
            Building dependency tree...
            Reading state information...
            Reading package lists...
            Building dependency tree...
            Reading state information...
            0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
            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 38224fdc84de... The host for instance "system.adapter.admin.0" was changed from "buildkitsandbox" to "38224fdc84de".
            The host for instance "system.adapter.discovery.0" was changed from "buildkitsandbox" to "38224fdc84de".
            The host for instance "system.adapter.backitup.0" was changed from "buildkitsandbox" to "38224fdc84de".
            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 see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).


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

            Starting ioBroker...

            host.38224fdc84de check instance "system.adapter.admin.0" for host "38224fdc84de"
            host.38224fdc84de check instance "system.adapter.discovery.0" for host "38224fdc84de"
            host.38224fdc84de check instance "system.adapter.backitup.0" for host "38224fdc84de"
            object system.meta.uuid created: 50e10132-4317-44cd-b226-416b149c510d
            ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging]
            Send diag info: {"uuid":"50e10132-4317-44cd-b226-416b149c510d","language":"de","country":"Germany","hosts":[{"version":"4.0.23","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.17.0","arch":"arm64","docker":true,"adapters":{"admin":{"version":"5.3.8","platform":"Javascript/Node.js"},"discovery":{"version":"3.0.3","platform":"Javascript/Node.js"},"backitup":{"version":"2.4.9","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":3,"compactMode":false,"noCompactInstances":0,"model":"unknown","cpus":4,"mem":4124368896,"ostype":"Linux","city":"Mühlheim am Main"}
            ================================== > LOG REDIRECT system.adapter.jarvis.0 => true [system.adapter.jarvis.0.logging]
            ================================== > LOG REDIRECT system.adapter.jarvis.0 => false [Process stopped]
            ================================== > LOG REDIRECT system.adapter.jarvis.0 => false [system.adapter.jarvis.0.logging]
            ================================== > LOG REDIRECT system.adapter.jarvis.0 => true [system.adapter.jarvis.0.logging]
            URIError: Failed to decode param '%web_protocol%://localhost:%web_port%/vis/edit.html'
            at decodeURIComponent (<anonymous>)
            at decode_param (/opt/iobroker/node_modules/express/lib/router/layer.js:172:12)
            at Layer.match (/opt/iobroker/node_modules/express/lib/router/layer.js:148:15)
            at matchLayer (/opt/iobroker/node_modules/express/lib/router/index.js:585:18)
            at next (/opt/iobroker/node_modules/express/lib/router/index.js:226:15)
            at compression (/opt/iobroker/node_modules/compression/index.js:220:5)
            at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
            at trim_prefix (/opt/iobroker/node_modules/express/lib/router/index.js:328:13)
            at /opt/iobroker/node_modules/express/lib/router/index.js:286:9
            at Function.process_params (/opt/iobroker/node_modules/express/lib/router/index.js:346:12)

            Send diag info: {"uuid":"50e10132-4317-44cd-b226-416b149c510d","language":"de","country":"Germany","hosts":[{"version":"4.0.23","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.17.0","arch":"arm64","docker":true,"adapters":{"admin":{"version":"5.3.8","platform":"Javascript/Node.js"},"discovery":{"version":"3.0.3","platform":"Javascript/Node.js"},"backitup":{"version":"2.4.9","platform":"Javascript/Node.js"},"net-tools":{"version":"0.2.0","platform":"Javascript/Node.js"},"ping":{"version":"1.5.3","platform":"Javascript/Node.js"},"history":{"version":"2.2.0","platform":"Javascript/Node.js"},"web":{"version":"4.3.0","platform":"Javascript/Node.js"},"jarvis":{"version":"3.0.11","platform":"Javascript/Node.js"},"javascript":{"version":"6.0.0","platform":"Javascript/Node.js"},"vis":{"version":"1.4.15","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":10,"compactMode":false,"noCompactInstances":0,"model":"unknown","cpus":4,"mem":4124368896,"ostype":"Linux","city":"Mühlheim am Main","vis":0}

            R 1 Antwort Letzte Antwort
            0
            • B BennyBO

              @rewenode Erstmal Danke für Deine Antworten, wenn ich das so mache wie im Link macht er einen neuen Container (Neuinstallation) der dann zwar unter Port 8081 erreichbar ist, die Problematik bleibt beim Rest aber die Gleiche, vielleicht schaue ich mal nach Befehlen für das Port Mapping für Docker Desktop, hab damit nie wirklich gearbeitet, daher bin ich in dieser Angelegenheit leider nicht firm, oder hast Du noch eine Idee ?

              Hier das was von Docker ausgeführt wurde:

              docker run -p 8081:8081 --name iobroker1 -v iobrokerdata:/opt/iobroker1 buanet/iobroker:latest


              ------------------------- 2022-09-09 10:56:06 -------------------------


              ----- Welcome to your ioBroker-container! -----
              ----- Startupscript is now running. -----
              ----- Please be patient! -----


              ----- Debugging information -----


              ----- System -----
              ----- arch: aarch64 -----
              ----- hostname: 38224fdc84de -----


              ----- Docker-Image -----
              ----- image: v7.0.1 -----
              ----- build: 2022-07-05T18:51:52+00:00 -----


              ----- Versions -----
              ----- node: v16.15.1 -----
              ----- npm: 8.11.0 -----


              ----- ENV -----
              ----- SETGID: 1000 -----
              ----- SETUID: 1000 -----


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

              Updating Linux packages on first run...
              dpkg-preconfigure: unable to re-open stdin:
              (Reading database ... 29325 files and directories currently installed.)
              Preparing to unpack .../base-files_11.1+deb11u4_arm64.deb ...
              Unpacking base-files (11.1+deb11u4) over (11.1+deb11u3) ...
              Setting up base-files (11.1+deb11u4) ...
              Installing new version of config file /etc/debian_version ...
              (Reading database ... 29325 files and directories currently installed.)
              Preparing to unpack .../bash_5.1-2+deb11u1_arm64.deb ...
              update-alternatives: warning: alternative /usr/share/man/man7/bash-builtins.7.gz (part of link group builtins.7.gz) doesn't exist; removing from list of alternatives
              update-alternatives: warning: /etc/alternatives/builtins.7.gz is dangling; it will be updated with best choice
              Unpacking bash (5.1-2+deb11u1) over (5.1-2+b3) ...
              Setting up bash (5.1-2+deb11u1) ...
              update-alternatives: error: alternative path /usr/share/man/man7/bash-builtins.7.gz doesn't exist
              (Reading database ... 29324 files and directories currently installed.)
              Preparing to unpack .../dpkg_1.20.11_arm64.deb ...
              Unpacking dpkg (1.20.11) over (1.20.10) ...
              Setting up dpkg (1.20.11) ...
              (Reading database ... 29324 files and directories currently installed.)
              Preparing to unpack .../libgnutls30_3.7.1-5+deb11u2_arm64.deb ...
              Unpacking libgnutls30:arm64 (3.7.1-5+deb11u2) over (3.7.1-5) ...
              Setting up libgnutls30:arm64 (3.7.1-5+deb11u2) ...
              (Reading database ... 29324 files and directories currently installed.)
              Preparing to unpack .../libwbclient0_2%3a4.13.13+dfsg-1~deb11u5_arm64.deb ...
              Unpacking libwbclient0:arm64 (2:4.13.13+dfsg-1~deb11u5) over (2:4.13.13+dfsg-1~deb11u3) ...
              Preparing to unpack .../libssl1.1_1.1.1n-0+deb11u3_arm64.deb ...
              Unpacking libssl1.1:arm64 (1.1.1n-0+deb11u3) over (1.1.1n-0+deb11u2) ...
              Setting up libssl1.1:arm64 (1.1.1n-0+deb11u3) ...
              (Reading database ... 29324 files and directories currently installed.)
              Preparing to unpack .../libtirpc-common_1.3.1-1+deb11u1_all.deb ...
              Unpacking libtirpc-common (1.3.1-1+deb11u1) over (1.3.1-1) ...
              Setting up libtirpc-common (1.3.1-1+deb11u1) ...
              (Reading database ... 29324 files and directories currently installed.)
              Preparing to unpack .../libtirpc-dev_1.3.1-1+deb11u1_arm64.deb ...
              Unpacking libtirpc-dev:arm64 (1.3.1-1+deb11u1) over (1.3.1-1) ...
              Preparing to unpack .../libtirpc3_1.3.1-1+deb11u1_arm64.deb ...
              Unpacking libtirpc3:arm64 (1.3.1-1+deb11u1) over (1.3.1-1) ...
              Setting up libtirpc3:arm64 (1.3.1-1+deb11u1) ...
              (Reading database ... 29324 files and directories currently installed.)
              Preparing to unpack .../zlib1g-dev_1%3a1.2.11.dfsg-2+deb11u2_arm64.deb ...
              Unpacking zlib1g-dev:arm64 (1:1.2.11.dfsg-2+deb11u2) over (1:1.2.11.dfsg-2+deb11u1) ...
              Preparing to unpack .../zlib1g_1%3a1.2.11.dfsg-2+deb11u2_arm64.deb ...
              Unpacking zlib1g:arm64 (1:1.2.11.dfsg-2+deb11u2) over (1:1.2.11.dfsg-2+deb11u1) ...
              Setting up zlib1g:arm64 (1:1.2.11.dfsg-2+deb11u2) ...
              (Reading database ... 29324 files and directories currently installed.)
              Preparing to unpack .../00-tzdata_2021a-1+deb11u5_all.deb ...
              Unpacking tzdata (2021a-1+deb11u5) over (2021a-1+deb11u4) ...
              Preparing to unpack .../01-curl_7.74.0-1.3+deb11u2_arm64.deb ...
              Unpacking curl (7.74.0-1.3+deb11u2) over (7.74.0-1.3+deb11u1) ...
              Preparing to unpack .../02-libcurl4_7.74.0-1.3+deb11u2_arm64.deb ...
              Unpacking libcurl4:arm64 (7.74.0-1.3+deb11u2) over (7.74.0-1.3+deb11u1) ...
              Preparing to unpack .../03-distro-info-data_0.51+deb11u2_all.deb ...
              Unpacking distro-info-data (0.51+deb11u2) over (0.51+deb11u1) ...
              Preparing to unpack .../04-dpkg-dev_1.20.11_all.deb ...
              Unpacking dpkg-dev (1.20.11) over (1.20.10) ...
              Preparing to unpack .../05-libdpkg-perl_1.20.11_all.deb ...
              Unpacking libdpkg-perl (1.20.11) over (1.20.10) ...
              Preparing to unpack .../06-libcurl3-gnutls_7.74.0-1.3+deb11u2_arm64.deb ...
              Unpacking libcurl3-gnutls:arm64 (7.74.0-1.3+deb11u2) over (7.74.0-1.3+deb11u1) ...
              Preparing to unpack .../07-libfreetype-dev_2.10.4+dfsg-1+deb11u1_arm64.deb ...
              Unpacking libfreetype-dev:arm64 (2.10.4+dfsg-1+deb11u1) over (2.10.4+dfsg-1) ...
              Preparing to unpack .../08-libfreetype6-dev_2.10.4+dfsg-1+deb11u1_arm64.deb ...
              Unpacking libfreetype6-dev:arm64 (2.10.4+dfsg-1+deb11u1) over (2.10.4+dfsg-1) ...
              Preparing to unpack .../09-libfreetype6_2.10.4+dfsg-1+deb11u1_arm64.deb ...
              Unpacking libfreetype6:arm64 (2.10.4+dfsg-1+deb11u1) over (2.10.4+dfsg-1) ...
              Preparing to unpack .../10-libfribidi-dev_1.0.8-2+deb11u1_arm64.deb ...
              Unpacking libfribidi-dev:arm64 (1.0.8-2+deb11u1) over (1.0.8-2) ...
              Preparing to unpack .../11-libfribidi0_1.0.8-2+deb11u1_arm64.deb ...
              Unpacking libfribidi0:arm64 (1.0.8-2+deb11u1) over (1.0.8-2) ...
              Preparing to unpack .../12-linux-libc-dev_5.10.136-1_arm64.deb ...
              Unpacking linux-libc-dev:arm64 (5.10.136-1) over (5.10.120-1) ...
              Preparing to unpack .../13-nodejs_16.17.0-deb-1nodesource1_arm64.deb ...
              Unpacking nodejs (16.17.0-deb-1nodesource1) over (16.15.1-deb-1nodesource1) ...
              Preparing to unpack .../14-unzip_6.0-26+deb11u1_arm64.deb ...
              Unpacking unzip (6.0-26+deb11u1) over (6.0-26) ...
              Setting up distro-info-data (0.51+deb11u2) ...
              Setting up unzip (6.0-26+deb11u1) ...
              Setting up linux-libc-dev:arm64 (5.10.136-1) ...
              Setting up libcurl3-gnutls:arm64 (7.74.0-1.3+deb11u2) ...
              Setting up nodejs (16.17.0-deb-1nodesource1) ...
              Setting up libwbclient0:arm64 (2:4.13.13+dfsg-1~deb11u5) ...
              Setting up tzdata (2021a-1+deb11u5) ...

              Current default time zone: 'Etc/UTC'
              Local time is now: Fri Sep 9 08:56:25 UTC 2022.
              Universal Time is now: Fri Sep 9 08:56:25 UTC 2022.
              Run 'dpkg-reconfigure tzdata' if you wish to change it.

              Setting up libtirpc-dev:arm64 (1.3.1-1+deb11u1) ...
              Setting up libfreetype6:arm64 (2.10.4+dfsg-1+deb11u1) ...
              Setting up libfribidi0:arm64 (1.0.8-2+deb11u1) ...
              Setting up libdpkg-perl (1.20.11) ...
              Setting up zlib1g-dev:arm64 (1:1.2.11.dfsg-2+deb11u2) ...
              Setting up libcurl4:arm64 (7.74.0-1.3+deb11u2) ...
              Setting up curl (7.74.0-1.3+deb11u2) ...
              Setting up libfribidi-dev:arm64 (1.0.8-2+deb11u1) ...
              Setting up dpkg-dev (1.20.11) ...
              Setting up libfreetype-dev:arm64 (2.10.4+dfsg-1+deb11u1) ...
              Setting up libfreetype6-dev:arm64 (2.10.4+dfsg-1+deb11u1) ...
              Processing triggers for libc-bin (2.31-13+deb11u3) ...
              Reading package lists...
              Building dependency tree...
              Reading state information...
              Reading package lists...
              Building dependency tree...
              Reading state information...
              0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
              Done.

              Registering maintenance script as command... Done.

              Installing additional packages is set by ENV.
              Checking the following Packages: ...
              Reading package lists...
              Building dependency tree...
              Reading state information...
              Reading package lists...
              Building dependency tree...
              Reading state information...
              0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
              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 38224fdc84de... The host for instance "system.adapter.admin.0" was changed from "buildkitsandbox" to "38224fdc84de".
              The host for instance "system.adapter.discovery.0" was changed from "buildkitsandbox" to "38224fdc84de".
              The host for instance "system.adapter.backitup.0" was changed from "buildkitsandbox" to "38224fdc84de".
              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 see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).


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

              Starting ioBroker...

              host.38224fdc84de check instance "system.adapter.admin.0" for host "38224fdc84de"
              host.38224fdc84de check instance "system.adapter.discovery.0" for host "38224fdc84de"
              host.38224fdc84de check instance "system.adapter.backitup.0" for host "38224fdc84de"
              object system.meta.uuid created: 50e10132-4317-44cd-b226-416b149c510d
              ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging]
              Send diag info: {"uuid":"50e10132-4317-44cd-b226-416b149c510d","language":"de","country":"Germany","hosts":[{"version":"4.0.23","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.17.0","arch":"arm64","docker":true,"adapters":{"admin":{"version":"5.3.8","platform":"Javascript/Node.js"},"discovery":{"version":"3.0.3","platform":"Javascript/Node.js"},"backitup":{"version":"2.4.9","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":3,"compactMode":false,"noCompactInstances":0,"model":"unknown","cpus":4,"mem":4124368896,"ostype":"Linux","city":"Mühlheim am Main"}
              ================================== > LOG REDIRECT system.adapter.jarvis.0 => true [system.adapter.jarvis.0.logging]
              ================================== > LOG REDIRECT system.adapter.jarvis.0 => false [Process stopped]
              ================================== > LOG REDIRECT system.adapter.jarvis.0 => false [system.adapter.jarvis.0.logging]
              ================================== > LOG REDIRECT system.adapter.jarvis.0 => true [system.adapter.jarvis.0.logging]
              URIError: Failed to decode param '%web_protocol%://localhost:%web_port%/vis/edit.html'
              at decodeURIComponent (<anonymous>)
              at decode_param (/opt/iobroker/node_modules/express/lib/router/layer.js:172:12)
              at Layer.match (/opt/iobroker/node_modules/express/lib/router/layer.js:148:15)
              at matchLayer (/opt/iobroker/node_modules/express/lib/router/index.js:585:18)
              at next (/opt/iobroker/node_modules/express/lib/router/index.js:226:15)
              at compression (/opt/iobroker/node_modules/compression/index.js:220:5)
              at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
              at trim_prefix (/opt/iobroker/node_modules/express/lib/router/index.js:328:13)
              at /opt/iobroker/node_modules/express/lib/router/index.js:286:9
              at Function.process_params (/opt/iobroker/node_modules/express/lib/router/index.js:346:12)

              Send diag info: {"uuid":"50e10132-4317-44cd-b226-416b149c510d","language":"de","country":"Germany","hosts":[{"version":"4.0.23","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.17.0","arch":"arm64","docker":true,"adapters":{"admin":{"version":"5.3.8","platform":"Javascript/Node.js"},"discovery":{"version":"3.0.3","platform":"Javascript/Node.js"},"backitup":{"version":"2.4.9","platform":"Javascript/Node.js"},"net-tools":{"version":"0.2.0","platform":"Javascript/Node.js"},"ping":{"version":"1.5.3","platform":"Javascript/Node.js"},"history":{"version":"2.2.0","platform":"Javascript/Node.js"},"web":{"version":"4.3.0","platform":"Javascript/Node.js"},"jarvis":{"version":"3.0.11","platform":"Javascript/Node.js"},"javascript":{"version":"6.0.0","platform":"Javascript/Node.js"},"vis":{"version":"1.4.15","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":10,"compactMode":false,"noCompactInstances":0,"model":"unknown","cpus":4,"mem":4124368896,"ostype":"Linux","city":"Mühlheim am Main","vis":0}

              R Offline
              R Offline
              rewenode
              schrieb am zuletzt editiert von
              #6

              @bennybo sagte in ioBroker - DockerContainer MacOS Ports nicht erreichbar:

              Hier das was von Docker ausgeführt wurde:
              docker run -p 8081:8081 --name iobroker1 -v iobrokerdata:/opt/iobroker1 buanet/iobroker:latest

              Falls du nicht mit docker compose arbeitetst (was einfacher wäre) must du den RUN Befehl entsprechend ergänzen.

              docker run -p 8081:8081 -p 8082:8082 -p 8084:8084 --name iobroker1 -v iobrokerdata:/opt/iobroker1 buanet/iobroker:latest
              

              usw.
              Allgemein gilt für das Portmapping

              -p dockerHostPort :containerPort

              B 1 Antwort Letzte Antwort
              1
              • R rewenode

                @bennybo sagte in ioBroker - DockerContainer MacOS Ports nicht erreichbar:

                Hier das was von Docker ausgeführt wurde:
                docker run -p 8081:8081 --name iobroker1 -v iobrokerdata:/opt/iobroker1 buanet/iobroker:latest

                Falls du nicht mit docker compose arbeitetst (was einfacher wäre) must du den RUN Befehl entsprechend ergänzen.

                docker run -p 8081:8081 -p 8082:8082 -p 8084:8084 --name iobroker1 -v iobrokerdata:/opt/iobroker1 buanet/iobroker:latest
                

                usw.
                Allgemein gilt für das Portmapping

                -p dockerHostPort :containerPort

                B Offline
                B Offline
                BennyBO
                schrieb am zuletzt editiert von BennyBO
                #7

                @rewenode said in ioBroker - DockerContainer MacOS Ports nicht erreichbar:

                Bildschirmfoto 2022-09-09 um 11.41.26.png

                Was soll ich sagen?!?!!? Du bist mein Held heute, 1000000x Danke, es funktioniert !!!!
                Weiter gehts ;-)

                Zur Ergänzung für alle Anderen die vielleicht auch mal das Problem bekommen:

                docker run -p 80:80 -p 8081:8081 -p 8082:8082 -p 8084:8084 --name iobroker1 -v iobrokerdata:/opt/iobroker1 buanet/iobroker:latest

                Und schon läuft die Kiste.... und nochmal ... Tausend Dank an Reiner für den Support !!!!!!!!

                1 Antwort Letzte Antwort
                1
                Antworten
                • In einem neuen Thema antworten
                Anmelden zum Antworten
                • Älteste zuerst
                • Neuste zuerst
                • Meiste Stimmen


                Support us

                ioBroker
                Community Adapters
                Donate

                592

                Online

                32.6k

                Benutzer

                81.9k

                Themen

                1.3m

                Beiträge
                Community
                Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                ioBroker Community 2014-2025
                logo
                • Anmelden

                • Du hast noch kein Konto? Registrieren

                • Anmelden oder registrieren, um zu suchen
                • Erster Beitrag
                  Letzter Beitrag
                0
                • Home
                • Aktuell
                • Tags
                • Ungelesen 0
                • Kategorien
                • Unreplied
                • Beliebt
                • GitHub
                • Docu
                • Hilfe