Fix compatibility of Lakeouse Turbo on As-app with Podman 5
Details
| Detail name | Value |
|---|---|
| Changelog Number | 31346 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | C4 4.30.0, Exasol 2026.1.0, C4 4.29.6, C4 4.31.0 |
| Fix Versions | Exasol 2026.1.2 |
| Resolution Date | 2026-09-14 |
Description
On an As-app deployment with a version of Podman equal to or higher than 5.x, the systemd unit for the Lakehouse Turbo service failed to start. This is due to a change in the defaults and allowed parameters for Quadlets in newer versions of Podman.
Workaround
The systemd unit file is generated automatically when activating the service. However, it is possible to apply a fix manually and restart the service. For that, first locate the .container file with
systemctl --user show -P SourcePath exasol-dlhc.service
and edit it with the following:
- Under the section [Container], add
- Replace the HealthCmd parameter with
Network=pasta:-a,10.0.2.0,-n,255.255.255.0,-g,10.0.2.2
HealthCmd=curl -kf https://localhost:8443/actuator/health || exit 1
Afterwards, reload and restart the service
systemctl --user daemon-reload systemctl --user restart exasol-dlhc.service
This fix should be applied in each node. However, it is only temporary, since if the service is deactivated and activated again the .container file will be regenerated.
Fix
The generated unit is now compatible both with Podman 4.x and 5.x.
