Continuing NS8 Nextcloud + other problems

stephdl · May 2, 2025, 1:13pm

this is an example with piler

imageroot/systemd/user/piler-app.service

8d71a1e57


      
          [Unit]
          Description=Podman  piler-app.service
          BindsTo=piler.service
          After=piler.service mariadb-app.service memcached-app.service
          
          [Service]
          Environment=PODMAN_SYSTEMD_UNIT=%n
          EnvironmentFile=%S/state/environment
          WorkingDirectory=%S/state
          Restart=always
          TimeoutStopSec=70
          ExecStartPre=/bin/mkdir -p %S/state/piler_etc
          ExecStartPre=/usr/local/bin/runagent expand-configuration
          ExecStartPre=/bin/rm -f %t/piler-app.pid %t/piler-app.ctr-id
          ExecStart=/usr/bin/podman run --conmon-pidfile %t/piler-app.pid \
              --cidfile %t/piler-app.ctr-id --cgroups=no-conmon \
              --pod-id-file %t/piler.pod-id --replace -d --name  piler-app \
              --volume %S/state/piler_etc/config-site.php:/etc/piler/config-site.php:Z \
              --volume %S/state/piler_etc/piler.conf:/etc/piler/piler.conf:Z \
              --volume piler_etc:/etc/piler:Z \
              --volume piler_manticore:/var/piler/manticore:Z \

if not present you take the default value, if enable you can increase the time before the service gives up

keep in mind that you cannot add 120s like that, probably another service is waiting for this service to be up to do some requires on it.

We ask SSD because when a service starts, it is a mini OS that is starting, A container is just a specialized operating system, that is running inside your operating system.