home.social

#execstart — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #execstart, aggregated by home.social.

  1. Running Node-RED in a Python Virtual Environment

    blog.hardill.me.uk/2025/09/10/

    Recent changes to Raspberry Pi OS show the following error if you try to use `pip` to install a Python module

    pi@raspberypi:~ $ pip install RPi.GPIO

    error: externally-managed-environment

    × This environment is externally managed

    ╰─> To install Python packages system-wide, try apt install

    python3-xyz, where xyz is the package you are trying to

    install.

    If you wish to […]

    #Environment #ExecStart #ExecStartPre #nodeRed #python #raspberryPi #StandardOutput

  2. Running Node-RED in a Python Virtual Environment

    blog.hardill.me.uk/2025/09/10/

    Recent changes to Raspberry Pi OS show the following error if you try to use `pip` to install a Python module

    pi@raspberypi:~ $ pip install RPi.GPIO

    error: externally-managed-environment

    × This environment is externally managed

    ╰─> To install Python packages system-wide, try apt install

    python3-xyz, where xyz is the package you are trying to

    install.

    If you wish to […]

    #Environment #ExecStart #ExecStartPre #nodeRed #python #raspberryPi #StandardOutput

  3. Running Node-RED in a Python Virtual Environment

    blog.hardill.me.uk/2025/09/10/

    Recent changes to Raspberry Pi OS show the following error if you try to use `pip` to install a Python module

    pi@raspberypi:~ $ pip install RPi.GPIO

    error: externally-managed-environment

    × This environment is externally managed

    ╰─> To install Python packages system-wide, try apt install

    python3-xyz, where xyz is the package you are trying to

    install.

    If you wish to […]

    #Environment #ExecStart #ExecStartPre #nodeRed #python #raspberryPi #StandardOutput

  4. Running Node-RED in a Python Virtual Environment

    blog.hardill.me.uk/2025/09/10/

    Recent changes to Raspberry Pi OS show the following error if you try to use `pip` to install a Python module

    pi@raspberypi:~ $ pip install RPi.GPIO

    error: externally-managed-environment

    × This environment is externally managed

    ╰─> To install Python packages system-wide, try apt install

    python3-xyz, where xyz is the package you are trying to

    install.

    If you wish to […]

    #Environment #ExecStart #ExecStartPre #nodeRed #python #raspberryPi #StandardOutput

  5. Running Node-RED in a Python Virtual Environment

    blog.hardill.me.uk/2025/09/10/

    Recent changes to Raspberry Pi OS show the following error if you try to use `pip` to install a Python module

    pi@raspberypi:~ $ pip install RPi.GPIO

    error: externally-managed-environment

    × This environment is externally managed

    ╰─> To install Python packages system-wide, try apt install

    python3-xyz, where xyz is the package you are trying to

    install.

    If you wish to […]

    #Environment #ExecStart #ExecStartPre #nodeRed #python #raspberryPi #StandardOutput

  6. @whydoesnothingwork Thanks 🙏 Really good clear useful video of how modules are needed / used in with the to set ( etc. ) parameters using and for an application / providing a .

  7. @whydoesnothingwork Thanks 🙏 Really good clear useful video of how modules are needed / used in #nixos with the #configurationdotnix to set ( #port #ipaddress etc. ) parameters using #execstart and #systemd for an application / #package #clouddns providing a #service .

  8. @whydoesnothingwork Thanks 🙏 Really good clear useful video of how modules are needed / used in #nixos with the #configurationdotnix to set ( #port #ipaddress etc. ) parameters using #execstart and #systemd for an application / #package #clouddns providing a #service .

  9. @whydoesnothingwork Thanks 🙏 Really good clear useful video of how modules are needed / used in #nixos with the #configurationdotnix to set ( #port #ipaddress etc. ) parameters using #execstart and #systemd for an application / #package #clouddns providing a #service .

  10. @whydoesnothingwork Thanks 🙏 Really good clear useful video of how modules are needed / used in #nixos with the #configurationdotnix to set ( #port #ipaddress etc. ) parameters using #execstart and #systemd for an application / #package #clouddns providing a #service .

  11. TIL: If your /var/ partition fills up completely with #Docker images, you can use a different mount point for Docker data. Just change this line in /lib/systemd/system/docker.service (after stopping docker, and rsyncing all /var/lib/docker contents over)

    ExecStart=/usr/bin/dockerd --data-root /media/dennis/64GB_SD_EXT4/docker -H fd:// --containerd=/run/containerd/containerd.sock

    #ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

    I ran into this issue with my #NVIDIA Xavier whose root disk starts with only 11GB free.

  12. TIL: If your /var/ partition fills up completely with #Docker images, you can use a different mount point for Docker data. Just change this line in /lib/systemd/system/docker.service (after stopping docker, and rsyncing all /var/lib/docker contents over)

    ExecStart=/usr/bin/dockerd --data-root /media/dennis/64GB_SD_EXT4/docker -H fd:// --containerd=/run/containerd/containerd.sock

    #ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

    I ran into this issue with my #NVIDIA Xavier whose root disk starts with only 11GB free.

  13. TIL: If your /var/ partition fills up completely with #Docker images, you can use a different mount point for Docker data. Just change this line in /lib/systemd/system/docker.service (after stopping docker, and rsyncing all /var/lib/docker contents over)

    ExecStart=/usr/bin/dockerd --data-root /media/dennis/64GB_SD_EXT4/docker -H fd:// --containerd=/run/containerd/containerd.sock

    #ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

    I ran into this issue with my #NVIDIA Xavier whose root disk starts with only 11GB free.

  14. TIL: If your /var/ partition fills up completely with #Docker images, you can use a different mount point for Docker data. Just change this line in /lib/systemd/system/docker.service (after stopping docker, and rsyncing all /var/lib/docker contents over)

    ExecStart=/usr/bin/dockerd --data-root /media/dennis/64GB_SD_EXT4/docker -H fd:// --containerd=/run/containerd/containerd.sock

    #ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

    I ran into this issue with my #NVIDIA Xavier whose root disk starts with only 11GB free.

  15. TIL: If your /var/ partition fills up completely with #Docker images, you can use a different mount point for Docker data. Just change this line in /lib/systemd/system/docker.service (after stopping docker, and rsyncing all /var/lib/docker contents over)

    ExecStart=/usr/bin/dockerd --data-root /media/dennis/64GB_SD_EXT4/docker -H fd:// --containerd=/run/containerd/containerd.sock

    #ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

    I ran into this issue with my #NVIDIA Xavier whose root disk starts with only 11GB free.

  16. @p @sjw @Moon @graf

    seeing how simple that is, a "nice" systemd user unit script I made is a tangled mess >contains a link to stack overflow because I still don't know how the hell certain lines are supposed to work

    # ~/.config/systemd/user/[email protected]
    
    # Setup:
    #	loginctl enable-linger "${USER}"
    #	systemctl --user daemon-reload
    #	systemctl --user enable --now minecraft@'-var-minecraft-my\x2dsmp'.service
    
    [Unit]
    Description=Minecraft Server (%I)
    After=network.target
    
    [Service]
    Type=simple
    WorkingDirectory=%I
    KillSignal=SIGINT
    #ExecStart=sh start.sh
    ExecStart=java -jar server.jar
    SuccessExitStatus=INT SIGINT 130
    # https://serverfault.com/a/800631/175102
    Restart=always
    RestartSec=90
    StartLimitIntervalSec=400
    StartLimitBurst=3
    
    [Install]
    WantedBy=default.target

    >all this just so that I can have the logs stored in a corruptible binary format