docker-compose stop not working after docker-compose -p <name> up

Question

I am using docker-compose version 2. I am starting containers with docker-compose -p some_name up -d and trying to kill them with docker-compose stop. The commands exits with 0 code but the containers are still up and running.

Is this the expected behaviour for version? If yes, any idea how can I work around it?

my docker-compose.yml file looks like this

version: '2'
services:

  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:5.3.0
    ports:
      - "9200:9200"
    environment:
      ES_JAVA_OPTS: "-Xmx512m -Xms512m"
      xpack.security.enabled: "false"
      xpack.monitoring.enabled: "false"
      xpack.graph.enabled: "false"
      xpack.watcher.enabled: "false"
    ulimits:
      memlock:
        soft: -1
        hard: -1
      nofile:
        soft: 262144
        hard: 262144

  kafka-server:
    image: spotify/kafka
    environment:
      - TOPICS=my-topic
    ports:
     - "9092:9092"

  test:
    build: .
    depends_on:
      - elasticsearch
      - kafka-server

update

I found that the problem is caused by using the -p parameter and giving explicit prefix to the container. Still looking for the best way to solve it.

Answer 1

docker-compose -p [project_name] stop worked in my case. I had the same problem.