`init:true` supposedly still required for docker-compose

Accordingly to @luciodaou the flag init: true still required when using docker-compose.

But in my tests I could find any error, this was my stack of tests:

In Ubuntu Server 22.04 LTS, Dockerfile updated as version (commit 5edc4b2ad81629b3a602f78ceddf887e3c274c90), docker-compose.yml with the following:

version: "3.8"

services:
  1090merge:
    build:
      dockerfile: Dockerfile
    environment:
      - HOSTS=192.168.1.100,192.168.1.101,192.168.1.102

With $ docker compose up I've got:

[+] Building 0.0s (0/0)                                                                                                                              
[+] Running 1/0
 ✔ Container 1090merge-1090merge-1  Recreated                                                                                                   0.1s 
Attaching to 1090merge-1090merge-1
1090merge-1090merge-1  | Capturing SBS data from 192.168.1.100
1090merge-1090merge-1  | Capturing SBS data from 192.168.1.101
1090merge-1090merge-1  | Capturing SBS data from 192.168.1.102
1090merge-1090merge-1  | crond 4.5 dillon's cron daemon, started with loglevel notice
^CGracefully stopping... (press Ctrl+C again to force)
Aborting on container exit...
[+] Stopping 1/1
 ✔ Container 1090merge-1090merge-1  Stopped                                                                                                    10.2s 
canceled

(kept running for 5 minutes before Ctrl+C and for obvious reasons the IP were changed for sample data)

With that, @luciodaou can you check --no-cache and put your details here for debugging?

saviobatista / 1090merge

`init:true` supposedly still required for docker-compose #6