Error launch docker in wsl

General Discussions
1

Hello,

I pull my image from artifcatory then I create my container but now when I try to view logs container I found this error:

/usr/lib/python2.7/site-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a “-c” argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching ’
2023-09-08 15:46:38,620 CRIT Supervisor running as root (no user in config file)
2023-09-08 15:46:38,631 INFO RPC interface ‘supervisor’ initialized
2023-09-08 15:46:38,631 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
2023-09-08 15:46:38,631 INFO supervisord started with pid 8
2023-09-08 15:46:39,633 INFO spawnerr: can’t find command ‘/usr/sbin/cron’
2023-09-08 15:46:39,634 INFO spawned: ‘apache2’ with pid 11
2023-09-08 15:46:39,635 INFO spawnerr: can’t find command ‘/postfix.sh’
2023-09-08 15:46:39,636 INFO spawnerr: can’t find command ‘/usr/sbin/rsyslogd’
2023-09-08 15:46:39,660 INFO exited: apache2 (exit status 1; not expected)
2023-09-08 15:46:40,661 INFO spawnerr: can’t find command ‘/usr/sbin/cron’
2023-09-08 15:46:40,662 INFO spawned: ‘apache2’ with pid 14
2023-09-08 15:46:40,663 INFO spawnerr: can’t find command ‘/postfix.sh’
2023-09-08 15:46:40,663 INFO spawnerr: can’t find command ‘/usr/sbin/rsyslogd’
2023-09-08 15:46:40,685 INFO exited: apache2 (exit status 1; not expected)
2023-09-08 15:46:42,688 INFO spawnerr: can’t find command ‘/usr/sbin/cron’
2023-09-08 15:46:42,689 INFO spawned: ‘apache2’ with pid 17
2023-09-08 15:46:42,690 INFO spawnerr: can’t find command ‘/postfix.sh’
2023-09-08 15:46:42,690 INFO spawnerr: can’t find command ‘/usr/sbin/rsyslogd’
2023-09-08 15:46:42,716 INFO exited: apache2 (exit status 1; not expected)
2023-09-08 15:46:45,720 INFO spawnerr: can’t find command ‘/usr/sbin/cron’
2023-09-08 15:46:45,721 INFO gave up: cron entered FATAL state, too many start retries too quickly
2023-09-08 15:46:45,722 INFO spawned: ‘apache2’ with pid 20
2023-09-08 15:46:45,723 INFO spawnerr: can’t find command ‘/postfix.sh’
2023-09-08 15:46:45,723 INFO gave up: master entered FATAL state, too many start retries too quickly
2023-09-08 15:46:45,724 INFO spawnerr: can’t find command ‘/usr/sbin/rsyslogd’
2023-09-08 15:46:45,724 INFO gave up: rsyslog entered FATAL state, too many start retries too quickly
2023-09-08 15:46:45,746 INFO exited: apache2 (exit status 1; not expected)
2023-09-08 15:46:46,748 INFO gave up: apache2 entered FATAL state, too many start retries too quickly

this is code docker-compose.yml:

version: '3.7'

services:
    web:
        network_mode: "bridge"
        image: x
        volumes:
            - ./back:/var/www/back
            - ./front:/var/www/front
            - ./public:/var/www/public
            - /etc/ssl/certs:/etc/ssl/certs
        privileged: true
        ports:
            - "17100:80"
            - "17105:8089"
        links:
            - "postgres:postgres"

    postgres:
        network_mode: "bridge"
        image: y
        restart: always
        environment:
            TZ: "Europe/Paris"
            POSTGRES_USER: user
            POSTGRES_PASSWORD: "user"
            POSTGRES_DB: user
        volumes:
            - ./datas:/var/www/datas
        ports:
            - "17101:5432"

container is running ,in wsl when i test curl localhost:17100 it render code html but in windws when i test localhost:17100 it render error curl: (52) Empty reply from server

2

Please so not share text content as screenshot. It makes it unnecessary harder to read.

Can you share why this is a problem of docker in wsl?
Can you share logs from another docker host where the exact same image is runng?

3

any help please for this error …

4

The error in your Docker container logs indicates missing commands like /usr/sbin/cron, /postfix.sh, and /usr/sbin/rsyslogd.

o resolve this issue, ensure your Docker image includes these dependencies, or modify your Docker Compose configuration to include the necessary services. Additionally, check your Windows firewall and networking settings to ensure that port 17100 is properly exposed to access the container.

This will help resolve the issue of receiving an “Empty reply from server” when trying to access the container from Windows.