caddy (exit status 2; not expected)

[vphutane]

while running the services via docker command, all the services runs fine without any issue
docker run --name kafka -e ADV_HOST=localhost -e RUNTESTS=0 -e SAMPLEDATA=0 -e FORWARDLOGS=0 -p 3030:3030 -p 9092:9092 -p 8081:8081 -p 8083:8083 -p 8082:8082 -p 2181:2181 -p 9581-9585:9581-9585 landoop/fast-data-dev:latest.

However if I run the same via docker-compose, it errors our at caddy
kafka_1 | Starting services.
kafka_1 | This is Lenses.io’s fast-data-dev. Kafka 2.5.1-L0 (Lenses.io's Kafka Distribution).
kafka_1 | You may visit http://127.0.0.1:3030 in about a minute.
kafka_1 | 2020-12-13 13:50:56,602 INFO Included extra file "/etc/supervisord.d/01-zookeeper.conf" during parsing
kafka_1 | 2020-12-13 13:50:56,602 INFO Included extra file "/etc/supervisord.d/02-broker.conf" during parsing
kafka_1 | 2020-12-13 13:50:56,602 INFO Included extra file "/etc/supervisord.d/03-schema-registry.conf" during parsing
kafka_1 | 2020-12-13 13:50:56,603 INFO Included extra file "/etc/supervisord.d/04-rest-proxy.conf" during parsing
kafka_1 | 2020-12-13 13:50:56,603 INFO Included extra file "/etc/supervisord.d/05-connect-distributed.conf" during parsing
kafka_1 | 2020-12-13 13:50:56,603 INFO Included extra file "/etc/supervisord.d/06-caddy.conf" during parsing
kafka_1 | 2020-12-13 13:50:56,603 INFO Set uid to user 0 succeeded
kafka_1 | 2020-12-13 13:50:56,912 INFO RPC interface 'supervisor' initialized
kafka_1 | 2020-12-13 13:50:56,912 CRIT Server 'unix_http_server' running without any HTTP authentication checking
kafka_1 | 2020-12-13 13:50:56,913 INFO supervisord started with pid 7
kafka_1 | 2020-12-13 13:50:57,917 INFO spawned: 'broker' with pid 127
kafka_1 | 2020-12-13 13:50:57,922 INFO spawned: 'caddy' with pid 128
kafka_1 | 2020-12-13 13:50:57,927 INFO spawned: 'connect-distributed' with pid 129
kafka_1 | 2020-12-13 13:50:57,931 INFO spawned: 'rest-proxy' with pid 130
kafka_1 | 2020-12-13 13:50:57,934 INFO spawned: 'schema-registry' with pid 132
kafka_1 | 2020-12-13 13:50:57,936 INFO spawned: 'zookeeper' with pid 136
kafka_1 | 2020-12-13 13:50:57,942 INFO exited: caddy (exit status 2; not expected)
kafka_1 | 2020-12-13 13:50:58,968 INFO success: broker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
kafka_1 | 2020-12-13 13:50:58,970 INFO spawned: 'caddy' with pid 511
kafka_1 | 2020-12-13 13:50:58,970 INFO success: connect-distributed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
kafka_1 | 2020-12-13 13:50:58,970 INFO success: rest-proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
kafka_1 | 2020-12-13 13:50:58,970 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
kafka_1 | 2020-12-13 13:50:58,970 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
kafka_1 | 2020-12-13 13:50:58,987 INFO exited: caddy (exit status 2; not expected)
kafka_1 | 2020-12-13 13:51:01,057 INFO spawned: 'caddy' with pid 929
kafka_1 | 2020-12-13 13:51:01,255 INFO exited: caddy (exit status 2; not expected)
^CGracefully stopping... (press Ctrl+C again to force)

My docker-compose file is as below:-
version: '3.6'
services:
kafka:
image: lensesio/fast-data-dev:latest
container_name: kafka_1
ports:
- 2181:2181 # zookeeper
- 3030:3030 # ui
- 9092:9092 # broker
- 8081:8081 # schema registry
- 8082:8082 # rest proxy
- 8083:8083 # kafka connect
environment:
- ADV_HOST=127.0.0.1
- SAMPLEDATA=0
- FORWARDLOGS=0
- RUNTESTS=0

[AJ]

I'm probably really late to this party, but I had a similar issue today and this docker-compose file worked for me.

version: '2'

services:
kafka-cluster:
image: landoop/fast-data-dev:latest
environment:
ADV_HOST: 127.0.0.1 # Change to 192.168.99.100 if using Docker Toolbox
RUNTESTS: 0 # Disable Running tests so the cluster starts faster
ports:
- 2181:2181 # Zookeeper
- 3030:3030 # Landoop UI
- 8081-8083:8081-8083 # REST Proxy, Schema Registry, Kafka Connect ports
- 9581-9585:9581-9585 # JMX Ports
- 9092:9092 # Kafka Broker

In my case I just updated the image tag, as the previous image cp3.3.0 kept throwing the same caddy (exit status 2; not expected) error