KomuSolutions/igot99issues
3
0
Issues 14 Projects 1 Wiki

Automatischer Neustart von Podman Containern #25

New Issue
Closed
opened 2024-04-08 06:50:54 +02:00 by lukas · 4 comments
lukas commented 2024-04-08 06:50:54 +02:00
Owner
Copy Link

Aufgrund der rootless und daemonless Natur von Podman, funktionieren restart-flags in Kommandos und Compose-files nicht. Dies führt dazu, dass bei einem server-reboot keine Container neu gestartet werden, was wiederum zu einer sehr langen Downtime von über 6h in der Nacht zum 8. April führte, da ich schlief :)

Aufgrund der rootless und daemonless Natur von Podman, funktionieren restart-flags in Kommandos und Compose-files nicht. Dies führt dazu, dass bei einem server-reboot keine Container neu gestartet werden, was wiederum zu einer sehr langen [Downtime von über 6h](https://status.libre.moe/incident/352208) in der Nacht zum 8. April führte, da ich schlief :)
lukas added the
Involves
Testing
Kind
Bug
Priority
High
Domain
libre.moe
 labels 2024-04-08 06:50:54 +02:00
lukas self-assigned this 2024-04-08 06:50:54 +02:00
lukas added this to the Issue Board project 2024-04-08 06:50:54 +02:00
leon commented 2024-04-08 11:02:54 +02:00
Owner
Copy Link

Quick Fix: Nicht schlafen

Aber ja, ich bin mit dem MC Server auch schon in das Problem gelaufen.

Quick Fix: Nicht schlafen Aber ja, ich bin mit dem MC Server auch schon in das Problem gelaufen.
lukas commented 2024-04-08 14:05:44 +02:00
Author
Owner
Copy Link

Wie hast du es da gelöst?

Wie hast du es da gelöst?
leon commented 2024-04-08 14:56:01 +02:00
Owner
Copy Link

Siehe Quick Fix

Siehe Quick Fix
lukas commented 2024-04-28 15:18:58 +02:00
Author
Owner
Copy Link

Fixed mit systemctl enable podman-restart.service. Dieser Service startet automatisch alle container mit einer restart policy von always

Fixed mit `systemctl enable podman-restart.service`. Dieser Service startet automatisch alle container mit einer restart policy von `always`
lukas closed this issue 2024-04-28 15:18:58 +02:00
lukas removed this from the Issue Board project 2024-12-17 12:27:47 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Breaking
Breaking change that won't be backward compatible
Domain
komu.boo
Domain
langrock.info
Domain
libre.moe
Involves
Documentation
Issue invovles changing the documentation
Involves
Security
This is security issue
Involves
Testing
Issue or pull request related to testing
Kind
Bug
Something is not working
Kind
Enhancement
Improve existing functionality
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Service
Element
Service
Gitea
Service
Matrix
Service
Nextcloud
Service
Seafile
Service
Szuru|Kirei
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Duplicate
This issue or pull request already exists
Status
Invalid
Invalid issue
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Status
Planned
Issue has been confirmed and is planned to be resolved
Status
Won't Fix
This issue won't be fixed
No Label
Domain
libre.moe
Involves
Testing
Kind
Bug
Priority
High
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
leon lukas
No Assignees lukas
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KomuSolutions/igot99issues#25
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?