Designing for Ephemerality: Managing State in Scalingo's Container Architecture
Learn how to handle data and state in Scalingo's container architecture to avoid data loss caused by ephemeral file systems and buildpack automation.
Loading…
ReadMeFeed / Community knowledge
#containers
Real questions. Useful conversations. Find the people who know your stack.
scalingoHow LeetCode Prevents Your Code from Crashing Their Servers
Explore the engineering behind LeetCode's judge system, from container isolation and cgroups to the challenges of multi-language resource calibration.
leetcode
Taming Memory Spikes with Linux cgroups v2: Beyond the Hard Limit
Stop relying solely on the OOM Killer. Learn how to use Linux cgroups v2 memory.low, memory.high, and memory.max to create a tiered resource strategy that throttles instead of crashes.
CentOS 8 Stream: Systemd Integration with Podman Containers
Goal To have a Podman container automatically start, stop, and restart on boot using a systemd unit file generated by podman generate systemd on CentOS 8 Stream. Constraints & Uncertainty The generated unit must include proper ExecStart and ExecStop directives, and optional resilience settings like Restart=always . The container may require additional sy
podman
centosPodman Quadlet and systemd restart policy conflict during healthcheck failures
When using Podman Quadlet to manage container lifecycles, the generator translates .container files into systemd unit files. While resource limits and basic restart directives map to cgroups and systemd directives, the interaction between Podman's internal healthcheck and systemd's restart logic remains ambiguous. n If a container fails a defined healthcheck