Error for up container

General Discussions
,
1

hello
cordial greetings

I am presenting an inconvenience when trying to do a practice where I upload a container to review a code. but when I launch the with docker-compose -d up it raises the containers but immediately lowers them. I am doing it with sonarqube. I upload the link of an image.

Thank you
for the collaboration

Captura de pantalla 2022-01-18 223858
Captura de pantalla 2022-01-18 2238581026×271 14.3 KB

2

Have you checked “docker logs NAME/ID” for that container?
Its failing for some reason

3

greetings comrade

If reviewing the logs, the same container name appears, I don’t know if I have to create the sonarnet work network first?

Thank you

4

The container woudnt start at all if not all networks that it want to use, existed.
but docker logs dosnt contain any logs WHY it exited?

can you share the docker-compose file ?

5

este es my docker-compose.yml

version: "3"

services:
  sonarqube:
    image: sonarqube:8.2-community
    depends_on:
      - db
    ports:
      - "0.0.0.0:9000:9000"
    networks:
      - sonarnet
    environment:
      - SONARQUBE_JDBC_URL=jdbc:postgresql://db:5432/sonar
      - SONARQUBE_JDBC_USERNAME=sonar
      - SONARQUBE_JDBC_PASSWORD=sonar
    volumes:
      #- sonarqube_conff:/opt/sonarqube/conf
      #- sonarqube_dataa:/opt/sonarqube/data
      #- sonarqube_extensionss:/opt/sonarqube/extensions
      #- sonarqube_bundled-pluginss:/opt/sonarqube/lib/bundled-plugins
      - sonarqube_data:/opt/sonarqube/data
      - sonarqube_extensions:/opt/sonarqube/extensions
      - sonarqube_logs:/opt/sonarqube/logs
      - sonarqube_temp:/opt/sonarqube/temp
  db:
    image: postgres
    networks:
      - sonarnet
    environment:
      - POSTGRES_USER=sonar
      - POSTGRES_PASSWORD=sonar
    volumes:
      - postgresqll:/var/lib/postgresql
      - postgresql_dataa:/var/lib/postgresql/data

networks:
  sonarnet:
     driver: bridge

volumes:
#sonarqube_conff:
#sonarqube_dataa:
#sonarqube_extensionss:
#sonarqube_bundled-pluginss:
postgresqll:
postgresql_dataa:
sonarqube_data:
sonarqube_extensions:
sonarqube_logs:
sonarqube_temp:
#postgresql:
#postgresql_data:
6

What you can try, is editing this line:

- sonarqube_logs:/opt/sonarqube/logs

to

- /tmp/logs:/opt/sonarqube/logs

and rerun: docker-compose up -d

and hopefully it will create some logs on the host filesystem at: /tmp/logs that will give some pointers on whats going on