Strona 23 z 84

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: pn maja 13, 2019 8:41 pm
autor: Esteta
Problem się rozwiązał.
Okazuje się, że jeżeli do Cloud'a nie ma dodanych żadnych urządzeń, to nie da się połączyć ze Skryptów.
Sporo straconego czasu, ale przynajmniej nauczyłem się paru rzeczy :)
Dzięki za pomoc.

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: pn maja 13, 2019 8:56 pm
autor: lesny8
A to nie tylko Ty jeden, bo ja też tego nie wiedziałem :)

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: śr maja 22, 2019 8:00 am
autor: superprzemo
Witam,

Usiłuję uruchomić SUPLA na dosyć leciwego RP B (pierwsze modele z 2 USB), na karcie mam wgrane "Raspbian Stretch with desktop", postępuję według instrukcji z pierwszej strony i przy komendzie

Kod: Zaznacz cały

sudo apt-get install -y docker-ce=18.03.0~ce-0~raspbian –allow-downgrades
otrzymuję:

Kod: Zaznacz cały

Czytanie list pakietów... Gotowe
Budowanie drzewa zależności
Odczyt informacji o stanie... Gotowe
E: Nie udało się odnaleźć pakietu –allow-downgrades
Mam wgrane:

Kod: Zaznacz cały

Docker version 18.09.0, build 4d60db4
docker-compose version 1.24.0, build 0aa5906
Jeżeli pomijam krok downgrade, to przy próbie odpalenia SUPLA, mam takie coś:

Kod: Zaznacz cały

Starting SUPLA containers
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?

If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
Co mam teraz zrobić, żeby ukończyć proces instalacji SUPLA na RP?

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: śr maja 22, 2019 10:02 am
autor: lesny8
Daj dwa myślniki przed allow-downgrades, był błąd

Kod: Zaznacz cały

sudo apt-get install -y docker-ce=18.03.0~ce-0~raspbian --allow-downgrades

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: śr maja 22, 2019 10:56 am
autor: superprzemo
Ok, poszło dalej, ale dostałem takie błędy przy .start/sh:

Kod: Zaznacz cały

pi@raspberrypi:~/docker-compose-letsencrypt-nginx-proxy-companion $ ./start.sh
d1e9a41c3485afc0a7a7478521c32006c70f08bcd59ad0979e1e2004d44af11e
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 16292  100 16292    0     0  14215      0  0:00:01  0:00:01 --:--:-- 14228
Pulling nginx-web         ... done
Pulling nginx-gen         ... done
Pulling nginx-letsencrypt ... done
Creating nginx-letsencrypt ...
Creating nginx-web         ...
Creating nginx-gen         ...

ERROR: for nginx-letsencrypt  UnixHTTPConnectionPool(host='localhost', port=None                                                                                                 ): Read timed out. (read timeout=60)

ERROR: for nginx-web  UnixHTTPConnectionPool(host='localhost', port=None): Read                                                                                                  timed out. (read timeout=60)

ERROR: for nginx-gen  UnixHTTPConnectionPool(host='localhost', port=None): Read                                                                                                  timed out. (read timeout=60)

ERROR: for nginx-web  UnixHTTPConnectionPool(host='localhost', port=None): Read                                                                                                  timed out. (read timeout=60)

ERROR: for nginx-gen  UnixHTTPConnectionPool(host='localhost', port=None): Read                                                                                                  timed out. (read timeout=60)

ERROR: for nginx-letsencrypt  UnixHTTPConnectionPool(host='localhost', port=None                                                                                                 ): Read timed out. (read timeout=60)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain                                                                                                  debug information.
If you encounter this issue regularly because of slow network conditions, consid                                                                                                 er setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
docker.ps:

Kod: Zaznacz cały

pi@raspberrypi:~/docker-compose-letsencrypt-nginx-proxy-companion $ docker ps
CONTAINER ID        IMAGE                                    COMMAND                  CREATED             STATUS                              PORTS                                      NAMES
9ed25548a43a        arm32v6/nginx:alpine                     "nginx -g 'daemon of…"   4 minutes ago       Up About a minute                   0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp   nginx-web
2d40069cc694        jwilder/docker-gen                       "/usr/local/bin/dock…"   4 minutes ago       Restarting (1) About a minute ago                                              nginx-gen
1c8aa9b31d76        jrcs/letsencrypt-nginx-proxy-companion   "/bin/bash /app/entr…"   4 minutes ago       Restarting (1) About a minute ago                                              nginx-letsencrypt
Próba odpalenia SUPLA:

Kod: Zaznacz cały

pi@raspberrypi:~ $ ./supla-docker/supla.sh start
Starting SUPLA containers
WARNING: The PORT_HTTP variable is not set. Defaulting to a blank string.
ERROR: The Compose file './docker-compose.standalone.yml' is invalid because:
services.supla-cloud.ports is invalid: Port ranges don't match in length
Co teraz mam zrobić?

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: śr maja 22, 2019 12:44 pm
autor: lesny8
superprzemo pisze: śr maja 22, 2019 10:56 am docker.ps:

Kod: Zaznacz cały

pi@raspberrypi:~/docker-compose-letsencrypt-nginx-proxy-companion $ docker ps
CONTAINER ID        IMAGE                                    COMMAND                  CREATED             STATUS                              PORTS                                      NAMES
9ed25548a43a        arm32v6/nginx:alpine                     "nginx -g 'daemon of…"   4 minutes ago       Up About a minute                   0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp   nginx-web
2d40069cc694        jwilder/docker-gen                       "/usr/local/bin/dock…"   4 minutes ago       Restarting (1) About a minute ago                                              nginx-gen
1c8aa9b31d76        jrcs/letsencrypt-nginx-proxy-companion   "/bin/bash /app/entr…"   4 minutes ago       Restarting (1) About a minute ago                                              nginx-letsencrypt
Na pewno nie zrobiłeś tego
lesny8 pisze: pn gru 03, 2018 1:19 am
Jako, że uruchamiamy to na RPI musimy zmienić obraz dla dwóch kontenerów, aby działał na naszej architekturze sprzętowej, bo bez tej zmiany nie zadziała. Robimy to jak w tym commicie.

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: śr maja 22, 2019 1:23 pm
autor: superprzemo
To mam w docker-compose.yml:

Kod: Zaznacz cały

version: '3'
services:
  nginx-web:
    image: arm32v6/nginx:alpine
    labels:
        com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
    container_name: ${NGINX_WEB:-nginx-web}
    restart: always
    ports:
      - "${IP:-0.0.0.0}:${DOCKER_HTTP:-80}:80"
      - "${IP:-0.0.0.0}:${DOCKER_HTTPS:-443}:443"
    volumes:
      - ${NGINX_FILES_PATH:-./data}/conf.d:/etc/nginx/conf.d
      - ${NGINX_FILES_PATH:-./data}/vhost.d:/etc/nginx/vhost.d
      - ${NGINX_FILES_PATH:-./data}/html:/usr/share/nginx/html
      - ${NGINX_FILES_PATH:-./data}/certs:/etc/nginx/certs:ro
      - ${NGINX_FILES_PATH:-./data}/htpasswd:/etc/nginx/htpasswd:ro
    logging:
      driver: ${NGINX_WEB_LOG_DRIVER:-json-file}
      options:
        max-size: ${NGINX_WEB_LOG_MAX_SIZE:-4m}
        max-file: ${NGINX_WEB_LOG_MAX_FILE:-10}

  nginx-gen:
    image: jwilder/docker-gen
    command: -notify-sighup ${NGINX_WEB:-nginx-web} -watch -wait 5s:30s /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
    container_name: ${DOCKER_GEN:-nginx-gen}
    restart: always
    volumes:
      - ${NGINX_FILES_PATH:-./data}/conf.d:/etc/nginx/conf.d
      - ${NGINX_FILES_PATH:-./data}/vhost.d:/etc/nginx/vhost.d
      - ${NGINX_FILES_PATH:-./data}/html:/usr/share/nginx/html
      - ${NGINX_FILES_PATH:-./data}/certs:/etc/nginx/certs:ro
      - ${NGINX_FILES_PATH:-./data}/htpasswd:/etc/nginx/htpasswd:ro
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - ./nginx.tmpl:/etc/docker-gen/templates/nginx.tmpl:ro
    logging:
      driver: ${NGINX_GEN_LOG_DRIVER:-json-file}
      options:
        max-size: ${NGINX_GEN_LOG_MAX_SIZE:-2m}
        max-file: ${NGINX_GEN_LOG_MAX_FILE:-10}

  nginx-letsencrypt:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: ${LETS_ENCRYPT:-nginx-letsencrypt}
    restart: always
    volumes:
	  - ${NGINX_FILES_PATH:-./data}/conf.d:/etc/nginx/conf.d
      - ${NGINX_FILES_PATH:-./data}/vhost.d:/etc/nginx/vhost.d
      - ${NGINX_FILES_PATH:-./data}/html:/usr/share/nginx/html
      - ${NGINX_FILES_PATH:-./data}/certs:/etc/nginx/certs:ro
      - ${NGINX_FILES_PATH:-./data}/htpasswd:/etc/nginx/htpasswd:ro
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - ./nginx.tmpl:/etc/docker-gen/templates/nginx.tmpl:ro
    logging:
      driver: ${NGINX_GEN_LOG_DRIVER:-json-file}
      options:
        max-size: ${NGINX_GEN_LOG_MAX_SIZE:-2m}
        max-file: ${NGINX_GEN_LOG_MAX_FILE:-10}

  nginx-letsencrypt:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: ${LETS_ENCRYPT:-nginx-letsencrypt}
    restart: always
    volumes:
      - ${NGINX_FILES_PATH:-./data}/conf.d:/etc/nginx/conf.d
      - ${NGINX_FILES_PATH:-./data}/vhost.d:/etc/nginx/vhost.d
      - ${NGINX_FILES_PATH:-./data}/html:/usr/share/nginx/html
      - ${NGINX_FILES_PATH:-./data}/certs:/etc/nginx/certs:rw
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      NGINX_DOCKER_GEN_CONTAINER: ${DOCKER_GEN:-nginx-gen}
      NGINX_PROXY_CONTAINER: ${NGINX_WEB:-nginx-web}
    logging:
      driver: ${NGINX_LETSENCRYPT_LOG_DRIVER:-json-file}
      options:
        max-size: ${NGINX_LETSENCRYPT_LOG_MAX_SIZE:-2m}
        max-file: ${NGINX_LETSENCRYPT_LOG_MAX_FILE:-10}

networks:
  default:
    external:
      name: ${NETWORK:-webproxy}
Coś jeszcze mam zmienić oprócz arm32v6/nginx:alpine?

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: śr maja 22, 2019 1:57 pm
autor: lesny8
Tak, jak w commicie podlinkowanym wyżej.
Zmiań obraz dla nginx-gen i nginx-letsencrypt.

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: śr maja 22, 2019 2:14 pm
autor: superprzemo
Ok, poszło dalej, w docker ps mam:

Kod: Zaznacz cały

pi@raspberrypi:~/docker-compose-letsencrypt-nginx-proxy-companion $ docker ps
CONTAINER ID        IMAGE                                                   COMMAND                  CREATED              STATUS              PORTS                                      NAMES
336f3e2714bc        wouterds/rpi-docker-letsencrypt-nginx-proxy-companion   "/bin/bash /app/entr…"   About a minute ago   Up 48 seconds                                                  nginx-letsencrypt
10f64b3244ea        wouterds/rpi-docker-gen                                 "/usr/local/bin/dock…"   2 minutes ago        Up About a minute                                              nginx-gen
9ed25548a43a        arm32v6/nginx:alpine                                    "nginx -g 'daemon of…"   4 hours ago          Up 4 hours          0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp   nginx-web
Przy próbie odpalenia kontenerów mam:

Kod: Zaznacz cały

pi@raspberrypi:~ $ ./supla-docker/supla.sh start
Starting SUPLA containers
WARNING: The PORT_HTTP variable is not set. Defaulting to a blank string.
ERROR: The Compose file './docker-compose.standalone.yml' is invalid because:
services.supla-cloud.ports is invalid: Port ranges don't match in length

Re: [tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

: śr maja 22, 2019 2:46 pm
autor: lesny8
Coś nie tak masz w plikach .yml
Przeczytaj jeszcze raz #4 i dostosuj pliki