Posts by aptalca

  • Install Nextcloud (LinuxServer.io)

    Check the log via "journalctl -u docker.linuxserver.nextcloud" and it should tell you what's going on with the creation and start of the container.

    A potential issue could be that port 443 is already taken so the container can't be started with that mapping. If that's the case, go into addon settings and change the port to something else that's not in use.

  • How to access portainer?

    Quote from darav

    Hi there,

    If I'm allowed to pick up an old thread, I'm also stuck on this issue. I am very new to docker and can't find a way to use portainer. Here is the log:

    I have no idea what the lsio network is...

    lsio is the custom docker network set up by the updater addon, which is a dependency for all the docker addons in the linuxserver repo.

    No idea why it says it doesn't exist. Try disabling and re-enabling the updater addon and check its log

  • How to disable docker updater addon when using portainer

    Quote from elonesna

    Automatic image update for docker containers is a very bad idea:

    • there are containers that may have incompatibilities with others and whose update must be executed in a certain order, and even stop some while updating another (example: my wireguard server must start after pihole)
    • updating a docker image can lead to an interruption of the streaming service (vpn, tv, video, ...)
    • updating a docker image always creates a risky situation that should not be left to an automatic timer

    It doesn't auto recreate containers. It only updates the image so none of those concerns are applicable here.

  • How to disable docker updater addon when using portainer

    Updater only automatically deletes orphaned images, such as the ones that lost their tag because a newer image was downloaded for that tag. It doesn't auto delete non orphaned images even if they are not attached to a container.

    libreelec-addon-repo/docker.linuxserver.updater at master · linuxserver/libreelec-addon-repo
    Contribute to linuxserver/libreelec-addon-repo development by creating an account on GitHub.
    github.com

    The prune button in the addon settings however does remove all images not attached to a container, but that is a manual operation, not automated.

    libreelec-addon-repo/settings.xml at master · linuxserver/libreelec-addon-repo
    Contribute to linuxserver/libreelec-addon-repo development by creating an account on GitHub.
    github.com

    In other words, updater's cron operation uses "docker image prune -f" whereas the manual button uses "docker image prune -af" with the "a" being the critical flag.

  • docker.linuxserver.nn : repo and wrapper-addons ready for LE 10 ?

    Yes, the addons are compatible with LE 10

    You don't have to install the repo from zip, it's included as an option in the LE repo. Just install the linuxserver repo from the LE repo first, and then go to linuxserver repo and you can install the docker wrapper addons.

    If it's not working after install, check the journalctl logs via "journalctl -u docker.linuxserver.portainer.service" or the systemd status via "systemctl status docker.linuxserver.portainer.service" in terminal

  • Docker + Nextcloud + External storage

    It should be fine because the ssd should be mounted before docker starts. Rpi4 has enough power for an external ssd. Not sure about rpi3, but you can use a powered sata adapter worst case.

    Keep in mind that rpi4 can also boot from an external ssd, so no need to deal with the sd card at all. A sata adapter with uasp does wonders for overall speed.

  • kodi + docker + nextcloud + mariadb => inter container communication issues

    root issue = the main issue

    Just tested on my machine

    Installed the mariadb addon (if it starts with no data in its config folder, it pops open the settings for password entry)

    Entered a root password, along with a db name, user name and user password.

    Installed nextcloud, didn't change any settings.

    Waited for both to be started up and gave it another minute (watched the logs until services were ready for both)

    Then I accessed the nextcloud gui on port 443 (https), put in a user and password, selected mysql/mariadb, entered the db and user details and for address, entered "mariadb:3306". Also unchecked the box for installing recommended apps. It connected fine and was set up within a minute or so (may take a few minutes on slower hardware).

    When I exec into nextcloud, I can ping "mariadb" successfully:

    Code
    # docker exec -it nextcloud ping mariadb
PING mariadb (172.19.0.2): 56 data bytes
64 bytes from 172.19.0.2: seq=0 ttl=64 time=0.119 ms
64 bytes from 172.19.0.2: seq=1 ttl=64 time=0.094 ms
64 bytes from 172.19.0.2: seq=2 ttl=64 time=0.121 ms
^C
--- mariadb ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.094/0.111/0.121 ms

    The /etc/resolv.conf in nextcloud contains the following:

    Code
    # docker exec -it nextcloud cat /etc/resolv.conf
search localdomain
nameserver 127.0.0.11
options ndots:0

    So really, out of the box, it should just work.