Skip to content

Startup fails due to certbot sudo command usage #8

@dhm116

Description

@dhm116

When running the compose up -d {service} command to try this out for the first time, this is what I saw:

nginx_1     |  ********** STARTING NGINX HTTPS/AUTH PROXY **********
nginx_1     |
nginx_1     |
nginx_1     | /www/entrypoint.sh: line 21: sudo: command not found

Here is my dumbed-down compose file:

version: "3"

services:

  nginx:
    image: justsml/ssl-proxy:latest
    ports:
      - "443:443"
    restart: unless-stopped
    volumes:
      - ./configs/nginx/certs:/certs
    environment:
      - HTTPS_PORT=443
      - SERVER_NAME=servicename.127.0.0.1.xip.io
      - UPSTREAM_TARGET=upstream.127.0.0.1.xip.io:4433
      - CERT_AUTO=true
      - CERT_PUBLIC_PATH=/certs/fullchain.pem
      - CERT_PRIVATE_PATH=/certs/privkey.pem
    depends_on:
      - servicename

It looks like perhaps sudo just needs to be removed from that script?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions