DuckDNS -> "Something went wrong"

  • Hey there,


    I can not install duckdns docker.


    installation:

    docker create \

    --name=duckdns \

    --dns=1.1.1.1 \

    -e PUID=998 \

    -e PGID=100 \

    -e TZ=Europe/Berlin \

    -e SUBDOMAINS=xxxxxxxxx \

    -e TOKEN=xxxxxxx \

    -e LOG_FILE=true \

    -v /var/lib/docker/duckdns:/config \

    --restart unless-stopped \

    ghcr.io/linuxserver/duckdns



    LOG:


    If other information are missing, please ask.

    Hopefully someone can help. :S

  • Bad idea to use PUID=998

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


    • Offizieller Beitrag

    maar10media I am curious, why are you using docker cli method and not docker-compose? I'm not saying it is wrong, but it seems that most on the forum use the docker-compose format to deploy containers, and thus you might get a bit more input regarding a solution if you went that route. Also, as gderf posted above puid=998 is the root admin user, and that is considered not the best practices for several reasons admin is just intended for use with the GUI. You should create a regular user in the Users tab of the GUI, giving you a user id of 1000 or above. Add that user to the ssh and sudo groups and you will make the "code gods" happy.

    System Backup Typo alert: Under the Linux section the command should be sudo umount /dev/sda1 NOT sudo unmount /dev/sda1

    Backup Data Disk to Backup Disk on Same Machine: In a Scheduled Job:rsync -av --delete /srv/dev-disk-by-uuid-f8814ed9-9a5c-4e1c-8830-426968c20ea3/ /srv/dev-disk-by-uuid-e67439d5-00a3-4942-bd5f-b84ab86aa850/ Don't forget trailing slashes, and BE CAREFUL. (HT: Getting Started with OMV5)

    Equipment - Thinkserver TS140, NanoPi M4 (v.1), Odroid XU4 (Using DietPi): PiHole

    Einmal editiert, zuletzt von Agricola ()

    • Offizieller Beitrag

    -v /var/lib/docker/duckdns:/config \

    I also noticed your docker storage path is pointing to your boot drive. This too could lead to problems down the road. It needs to be somewhere on a data disk, something like /srv/dev-disk-by...../docker/duckdns


    There are a couple of items in the example docker cli code that also differ from yours"

    1. The example above does not list a dns entry.
    2. The LOG_FILE variable is set to false, and is optional BTW.

    System Backup Typo alert: Under the Linux section the command should be sudo umount /dev/sda1 NOT sudo unmount /dev/sda1

    Backup Data Disk to Backup Disk on Same Machine: In a Scheduled Job:rsync -av --delete /srv/dev-disk-by-uuid-f8814ed9-9a5c-4e1c-8830-426968c20ea3/ /srv/dev-disk-by-uuid-e67439d5-00a3-4942-bd5f-b84ab86aa850/ Don't forget trailing slashes, and BE CAREFUL. (HT: Getting Started with OMV5)

    Equipment - Thinkserver TS140, NanoPi M4 (v.1), Odroid XU4 (Using DietPi): PiHole

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!