Hello, I have a similar interest to override the default launch behavior because I want these properties:
The reason that I do this is that I want the entrypoint script to terminate completely and leave system to run my application as a separate unit file (which I set up in my entrypoint script), but to preserve the system status as healthy (graceful exit; do not attempt to restart entrypoint).
However, since updating two of my devices to Resin OS 2.13.6+rev1 (from 2.12 on a Pi2 and Pi3 device), the launch service fails very early after loading any new container. Simply starting the unit interactively works without error.
root@raspberry-pi2-0e771b3:~# journalctl -u launch
-- Logs begin at Thu 2018-08-09 22:09:35 UTC, end at Fri 2018-08-10 05:17:52 UTC. --
Aug 09 22:09:38 raspberry-pi2-0e771b3 systemd: Starting Resin.io User Application...
Aug 09 22:09:39 raspberry-pi2-0e771b3 systemd: launch.service: Main process exited, code=exited, status=1/FAILURE
Aug 09 22:09:39 raspberry-pi2-0e771b3 systemd: Failed to start Resin.io User Application.
Aug 09 22:09:39 raspberry-pi2-0e771b3 systemd: launch.service: Unit entered failed state.
Aug 09 22:09:39 raspberry-pi2-0e771b3 systemd: launch.service: Failed with result 'exit-code'.
root@raspberry-pi2-0e771b3:~# systemctl start launch
root@raspberry-pi2-0e771b3:~# echo $?
root@raspberry-pi2-0e771b3:~# systemctl status launch
● launch.service - Resin.io User Application
Loaded: loaded (/etc/systemd/system/launch.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2018-08-10 07:18:58 SAST; 9min ago
Main PID: 196 (code=exited, status=0/SUCCESS)
Aug 10 07:18:58 raspberry-pi2-0e771b3 systemd: Started Resin.io User Application.
For completeness, how are the relevant portions of my Dockerfile:
ENV INITSYSTEM on
# Resin systemd
COPY ./config/systemd.launch.service /etc/systemd/system/launch.service.d/app_override.conf
For my Pi3 I use
Is there a way to get any more debugging information about why the launch service fails when launched upon container update? Just to emphasize, the launch service on both devices works as intended, without error if run interactively.