Install.sh file installation error

cloned the onpremise 21.3.0 repo and when i run install.sh file in wsl-bash in vs code, it is showing this error “An error occurred, caught SIGERR on line 250”.

can anyone please tell me how to resolve this error?

log file content:

:arrow_forward: Defining variables and helpers …

:arrow_forward: Parsing command line …

:arrow_forward: Setting up error handling …

:arrow_forward: Checking minimum requirements …

WARN: Recommended minimum RAM available to Docker is 7800 MB, found 6259 MB

:arrow_forward: Creating volumes for persistent storage …

Created sentry-data.

Created sentry-postgres.

Created sentry-redis.

Created sentry-zookeeper.

Created sentry-kafka.

Created sentry-clickhouse.

Created sentry-symbolicator.

:arrow_forward: Ensuring files from examples …

sentry/sentry.conf.py already exists, skipped creation.

sentry/config.yml already exists, skipped creation.

sentry/requirements.txt already exists, skipped creation.

symbolicator/config.yml already exists, skipped creation.

relay/config.yml already exists, skipped creation.

:arrow_forward: Generating secret key …

:arrow_forward: Replacing TSDB …

:arrow_forward: Fetching and updating Docker images …

Define and run multi-container applications with Docker.

Usage:

docker-compose [-f …] [options] [–] [COMMAND] [ARGS…]

docker-compose -h|–help

Options:

-f, --file FILE Specify an alternate compose file

                          (default: docker-compose.yml)

-p, --project-name NAME Specify an alternate project name

                          (default: directory name)

-c, --context NAME Specify a context name

–verbose Show more output

–log-level LEVEL Set log level (DEBUG, INFO, WARNING, ERROR, CRITICAL)

–no-ansi Do not print ANSI control characters

-v, --version Print version and exit

-H, --host HOST Daemon socket to connect to

–tls Use TLS; implied by --tlsverify

–tlscacert CA_PATH Trust certs signed only by this CA

–tlscert CLIENT_CERT_PATH Path to TLS certificate file

–tlskey TLS_KEY_PATH Path to TLS key file

–tlsverify Use TLS and verify the remote

–skip-hostname-check Don’t check the daemon’s hostname against the

                          name specified in the client certificate

–project-directory PATH Specify an alternate working directory

                          (default: the path of the Compose file)

–compatibility If set, Compose will attempt to convert keys

                          in v3 files to their non-Swarm equivalent (DEPRECATED)

–env-file PATH Specify an alternate environment file

Commands:

build Build or rebuild services

config Validate and view the Compose file

create Create services

down Stop and remove containers, networks, images, and volumes

events Receive real time events from containers

exec Execute a command in a running container

help Get help on a command

images List images

kill Kill containers

logs View output from containers

pause Pause services

port Print the public port for a port binding

ps List containers

pull Pull service images

push Push service images

restart Restart services

rm Remove stopped containers

run Run a one-off command

scale Set number of containers for a service

start Start services

stop Stop services

top Display the running processes

unpause Unpause services

up Create and start containers

version Show version information and quit

invalid reference format

:arrow_forward: Building and tagging Docker images …

Define and run multi-container applications with Docker.

Usage:

docker-compose [-f …] [options] [–] [COMMAND] [ARGS…]

docker-compose -h|–help

Options:

-f, --file FILE Specify an alternate compose file

                          (default: docker-compose.yml)

-p, --project-name NAME Specify an alternate project name

                          (default: directory name)

-c, --context NAME Specify a context name

–verbose Show more output

–log-level LEVEL Set log level (DEBUG, INFO, WARNING, ERROR, CRITICAL)

–no-ansi Do not print ANSI control characters

-v, --version Print version and exit

-H, --host HOST Daemon socket to connect to

–tls Use TLS; implied by --tlsverify

–tlscacert CA_PATH Trust certs signed only by this CA

–tlscert CLIENT_CERT_PATH Path to TLS certificate file

–tlskey TLS_KEY_PATH Path to TLS key file

–tlsverify Use TLS and verify the remote

–skip-hostname-check Don’t check the daemon’s hostname against the

                          name specified in the client certificate

–project-directory PATH Specify an alternate working directory

                          (default: the path of the Compose file)

–compatibility If set, Compose will attempt to convert keys

                          in v3 files to their non-Swarm equivalent (DEPRECATED)

–env-file PATH Specify an alternate environment file

Commands:

build Build or rebuild services

config Validate and view the Compose file

create Create services

down Stop and remove containers, networks, images, and volumes

events Receive real time events from containers

exec Execute a command in a running container

help Get help on a command

images List images

kill Kill containers

logs View output from containers

pause Pause services

port Print the public port for a port binding

ps List containers

pull Pull service images

push Push service images

restart Restart services

rm Remove stopped containers

run Run a one-off command

scale Set number of containers for a service

start Start services

stop Stop services

top Display the running processes

unpause Unpause services

up Create and start containers

version Show version information and quit

An error occurred, caught SIGERR on line 250

Cleaning up…

Looks like you have a problem with your docker-compose command.

I checked docker-compose command in bash. I think it’s working fine.

$ docker-compose
Define and run multi-container applications with Docker.

Usage:
docker-compose [-f …] [options] [–] [COMMAND] [ARGS…]
docker-compose -h|–help

Options:
-f, --file FILE Specify an alternate compose file
(default: docker-compose.yml)
-p, --project-name NAME Specify an alternate project name
(default: directory name)
-c, --context NAME Specify a context name
–verbose Show more output
–log-level LEVEL Set log level (DEBUG, INFO, WARNING, ERROR, CRITICAL)
–no-ansi Do not print ANSI control characters
-v, --version Print version and exit
-H, --host HOST Daemon socket to connect to

–tls Use TLS; implied by --tlsverify
–tlscacert CA_PATH Trust certs signed only by this CA
–tlscert CLIENT_CERT_PATH Path to TLS certificate file
–tlskey TLS_KEY_PATH Path to TLS key file
–tlsverify Use TLS and verify the remote
–skip-hostname-check Don’t check the daemon’s hostname against the
name specified in the client certificate
–project-directory PATH Specify an alternate working directory
(default: the path of the Compose file)
–compatibility If set, Compose will attempt to convert keys
in v3 files to their non-Swarm equivalent (DEPRECATED)
–env-file PATH Specify an alternate environment file

Commands:
build Build or rebuild services
config Validate and view the Compose file
create Create services
down Stop and remove containers, networks, images, and volumes
events Receive real time events from containers
exec Execute a command in a running container
help Get help on a command
images List images
kill Kill containers
logs View output from containers
pause Pause services
port Print the public port for a port binding
ps List containers
pull Pull service images
push Push service images
restart Restart services
rm Remove stopped containers
run Run a one-off command
scale Set number of containers for a service
start Start services
stop Stop services
top Display the running processes
unpause Unpause services
up Create and start containers
version Show version information and quit

Look at the logs you’ve shared here. It seems like docker-compose command is not able to accept/parse the arguments we pass to it and keeps printing out its help message.

Do you have an alias of some sorts?

yes. I checked it by running 3 times. different log files generated with same error.

This doesn’t tell me anything new regarding the situation. Could you have an alias or a special script named docker-compose that may not be forwarding the parameters passed to it?

Another alternative is docker-compose not being installed inside WSL and docker-compose.exe from your Windows host being used and getting confused.

I installed docker in wsl. But when i check the status it is showing this error “System has not been booted with systemd as init system (PID 1). Can’t operate.
Failed to connect to bus: Host is down”

I guess that’s your issue then? Btw have you tried using WSL2 instead? That’s what I’m using and the experience is quite smooth.

can you please tell me how to resolve that issue?

when I run the ./install.sh file it is showing
output:

:arrow_forward: Defining variables and helpers …

:arrow_forward: Parsing command line …

:arrow_forward: Setting up error handling …

:arrow_forward: Checking minimum requirements …
Cannot connect to the Docker daemon at tcp://0.0.0.0:2375. Is the docker daemon running?
An error occurred, caught SIGERR on line 110
Cleaning up…

for that when I run “sudo dockerd”
output:

INFO[2021-03-22T11:23:20.950245300+05:30] Starting up
failed to start daemon: pid file found, ensure docker is not running or delete /var/run/docker.pid

I’m just using Docker Desktop with WSL2 integration enabled. Then it just works (need to keep Docker running in the background from Windows side though)

I am also using Docker Desktop with WSL2 integration enabled. I am keeping Docker running in the background from windows side

@reddeiah then I don’t really know what else might be going on. You may have better chance asking around in Docker or Windows forums.