kevinskymountain
Customize timeout in docker compose
Reposted from General
I see three docker commands which set the timeout to shut a container down. There is stop_grace_period, COMPOSE_HTTP_TIMEOUT and a flag -t or -timeout. Which of these would I use in a user customized docker compose.yml to let the Plex app have a longer time before it is shut down? The default value of 10 seconds is not long enough and I get file corruption errors after doing a server reboot.
1 replies
Customizing docker compose for apps
If I customize the compose for an app from the app store will it be overwritten during Tipi updates or app updates? If that is the case where would you put user customizations?
Use case: adding an extension to FreshRss which adds other Docker images
5 replies
Docker compose fails after reboot
Part of this problem is not Tipi. I am running this on VmWare and when I shut the Ubuntu server down I think the system does not allow enough time for docker to shut down leading to file errors. I fixed the file errors with fsck but after reboot the server starts, tipi starts, other tipi apps start but plex does not start with this error
cat error.log
worker: 2024-05-22T00:21:56.969Z - error > An error occurred: Command failed: docker-compose --env-file /app-data/plex/app.env --project-name plex -f /data/apps/plex/docker-compose.yml -f /data/repos/29ca930bfdaffa1dfabf5726336380ede7066bc53297e3c0c868b27c97282903/apps/docker-compose.common.yml up --detach --force-recreate --remove-orphans --pull always
time="2024-05-22T00:21:56Z" level=warning msg="/data/apps/plex/docker-compose.yml:
version is obsolete"
time="2024-05-22T00:21:56Z" level=warning msg="/data/repos/29ca930bfdaffa1dfabf5726336380ede7066bc53297e3c0c868b27c97282903/apps/docker-compose.common.yml: version is obsolete"
unable to get image 'lscr.io/linuxserver/plex:1.40.2': Error response from daemon: layer does not exist
How do I fix the docker compose and how do I allow more time for the system to shut down docker?18 replies
Applied 3.1 update, still showing as available
Applied using cli but received permissions error on stopping the containers. However CLI indicated success but the update is not recognized by the tipi web page. How to resolve this docker permission error?
✗ Failed to stop containers. Please try to stop them manually
Debug: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdo cker.sock/v1.24/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.proj ect%3Druntipi%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied
5 replies
Tipi does not auto start since 2.05
My tipi.service looks like this
[Unit]
Description=tipi
Requires=docker.service multi-user.target
After=docker.service network-online.target dhcpd.service
[Service]
Restart=always
RemainAfterExit=yes
WorkingDirectory=/home/<user>/runtipi
ExecStart=/home/<user>/runtipi/scripts/runtipi-cli start
ExecStop=/home/<user>/runtipi/scripts/runtipi-cli stop
[Install]
WantedBy=multi-user.target
Yet tipi does not start after a reboot. However my apps do start which confuses me. I need to run this manually
sudo ./runtipi-cli start
running as Ubuntu 22.04.3
13 replies
Will Tipi see a symlink as a directory in Ubuntu?
Ubuntu 22.04.2 Default Tipi install
The default size of the Tipi partition appears to be about 100 Gb. It is mounted on root so I cannot unmount the partition to extend it as it is in use by many, many root processes. If I create a symlink to a new partition for some of the folders like movies that take up a lot of space will this work?
9 replies
Cannot install apps
Clean install on Ubuntu 22
Tipi starts and runs but when using any app in the library
2023-01-01T18:57:50.310Z > EventDispatcher: app 3gg4y2v failed with error: Starting app script
parse error: Expected separator between values at line 3, column 9
parse error: Expected separator between values at line 3, column 9
Any thoughts?
2 replies