Problem with automatic container start after reboot. Exited (143)

[SirTeddyBear]

I have a problem with the automatic start of a container. I added this line to root crontab:

@reboot /usr/bin/podman start container-evil

after reboot, the container appears stopped with:

Exited (143)

then i have to start it manually, podman start container-evil without any problems.

I checked container logs, no warnings or errors. also i checked the boot log without any error.
I have some more containers in the crontab, all start at boot time without issues.

In the other hand, i have pods using the systemd to autostart at boot time without any issues, but of course it doesn't make sense to use a pod for a single container that doesn't depend on others, using infra containers.

Manually create a systemd file, resolve the issue:

[Unit]
Description=Redis Podman container
Wants=syslog.service
[Service]
Restart=always
ExecStart=/usr/bin/podman start -a container-evil
ExecStop=/usr/bin/podman stop -t 10 container-evil
[Install]
WantedBy=multi-user.target

I tried sudo podman generate systemd --new --files --name container-evil, the automated systemd file service tool, but when i tried to enable generate errors.

Any idea?