The containers didn't seem to start correctly. Ple...
# general
The containers didn't seem to start correctly. Please run the following command to check containers that may have errored out: sudo docker-compose --env-file ./docker/clickhouse-setup/env/x86_64.env -f docker/clickhouse-setup/docker-compose.yaml ps -a
hey @User welcome to SigNoz community 👋 can you share what you see on doing
docker ps
Also, which OS are you running this on and what is the memory allocated to docker? SigNoz needs minimum 2GB of memory to be allocated
running on ubuntu
memory is also fine
output of
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 7a3380f010b2 portainer/portainer "/portainer" 3 months ago Up 27 hours>8000/tcp, :::8000->8000/tcp,>9000/tcp, :::9000->9000/tcp portainer
seems like container not showing
can you share output of
sudo docker-compose --env-file ./docker/clickhouse-setup/env/x86_64.env -f docker/clickhouse-setup/docker-compose.yaml ps -a
run it in signoz/deploy folder
yes running in same directory
sudo docker-compose --env-file ./docker/clickhouse-setup/env/x86_64.env -f docker/clickhouse-setup/docker-compose.yaml ps -a Define and run multi-container applications with Docker. Usage: docker-compose [-f <arg>...] [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) --verbose Show more output --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 (for example if your docker host is an IP address) --project-directory PATH Specify an alternate working directory (default: the path of the Compose file) Commands: build Build or rebuild services bundle Generate a Docker bundle from the Compose file 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 the Docker-Compose version information
this is the output after running the command
ok - checking
I just tried installing the latest version on Ubuntu and it installed fine
there's something specific about your machine/env which is causing issue
do you want to do a quick screenshare zoom call to see if I can figure out the issue?
this is the expected ouput
can you try running this -
docker-compose --env-file ./docker/clickhouse-setup/env/x86_64.env -f docker/clickhouse-setup/docker-compose.yaml ps -a
It seems docker compose didn't recognise the options when you ran it last
yes ,ok running
getting same out put
yes docker compose didn't recoginse the options