Docker-compose Shutdown issue in Centos

Docker Desktop
1

Docker-compose with django backend when run in CentOS keeps failing after working for sometime. The deployment config is as follows
Frontend: Angular
Backend: Django
Addons: Celery + Rabbitmq

Note: Only Backend service fails while executing while frontend works fine.

The Docker-compose.yml file is as follows. Any insight might be helpful. Thanks in advance:

version: '3'

services:
    backend:
        build: ./Backend/src/
        command: gunicorn compfie2.wsgi --bind 0.0.0.0:9000 --threads 2
        volumes:
            - ./Backend/src:/Backend
        ports:
            - "9000:9000"

    nginx:
        image: nginx:latest
        ports:
            - "8080:8080"
        depends_on:
            - backend

    rabbitmq:
        container_name: "rabbitmq"
        image: rabbitmq:3.8-management-alpine
        ports:
            - '5672:5672'
            - '15672:15672'

    celery:
        build:
            context: ./Backend/src/
        command: celery -A compfie2 worker -l info
        depends_on:
            - rabbitmq
    angular:
        build: ./Frontend/
        ports:
            - "4200:80"

`
2

I am afraid this is not enough information to get an idea of what might be wrong, especially since this appears to be a custom created image for a custom application.

Please share logs that show the actual error message and the lines surrounding it.

When you write “keeps failing after working for sometime”, you mean it was working with Docker Desktop for Linux before? If yes, with which version did it work and with which version doesn’t it work anymore? Furthermore, I am interested to understand what makes you conclude this behavior is caused by Docker Desktop for Linux and not the application itself.

3

The logs show no error message instead just simply not loading/registering anything. However, the application works in one Linux server while it fails in another server with similar configuration. The docker version is also the same in both server. By writing “fails”, I mean that the application builds properly with docker-compose up --build and the frontend angular works properly. The problem occurs with backend Django while angular tries to connect with Django.
Here’s the docker info for your reference (same for both servers):

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.9.1-docker)
  scan: Docker Scan (Docker Inc., v0.17.0)

Server:
 Server Version: 20.10.18
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
 runc version: v1.1.4-0-g5fd4c4d
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 3.10.0-1160.76.1.el7.x86_64
 Operating System: CentOS Linux 7 (Core)
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 3.642GiB
 Name: ip-12-12-1-41.ap-south-1.compute.internal
 ID: AC7V:I3UK:YZH5:PBNC:VXOF:LBJU:LI6R:WCS3:PX3U:MUPA:IKBX:ZUKB
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false