exit code 14 error in mongodb container, I'm using mongodb container with with volume path then received exit code 14 error

Question

version: "3"
services:
   mongo:
      image: mongo
      working_dir: /c/data/
      ports:
       - 27017:27017
      deploy:
        replicas: 1
      volumes:
        - /c/data/:/data/db

I am tried that above stack file and I'm receiving exit code 14 error please give me the solution about the error,

`working_dir` refers to a directory inside the container, not on the host. you need to make sure `/c/data/` can be created on the node where the container runs (it is quite a weird path...). It is generally better to avoid using host volumes when working with stacks. — Mihai, Sep 22 '20 at 07:18

score 11 · Answer 1 · answered Oct 29 '20 at 16:19

11

Delete everything from /c/data/, in case there are some data from older version of Mongo

answered Oct 29 '20 at 16:19

Ivan Nedelcev

182
7

Yes, it is work but do I have to delete it every time? If I delete everything from `/c/data/` then it's work so I start the db and the files are recreated. When I restart the db I get exit code 14 error. – capo11 Dec 09 '20 at 09:53
I guess so.. only in case of upgrade/downgrade's.. I didn't found any workarounds at the moment – Ivan Nedelcev Dec 10 '20 at 10:21
1

This worked for me, along with using the `-d` flag. – Austin Brown Jan 21 '21 at 16:28
4

If I was ok with deleting data, then why would I make shared volume? – Dims Jan 26 '21 at 11:47

Airton · Answer 2 · 2022-07-29T03:18:40.187

9

In your terminal:

docker system prune

Works for me. Kew Approves =)

*Please, be careful! it clears everything!!

edited Jul 29 '22 at 03:18

answered Nov 09 '21 at 18:31

Airton

91
1
4

1

works, it will clear the mess – Akshay Vijay Jain Apr 09 '22 at 18:14
1

This helped me quickly resolve a disk full issue today. But i would advise that you proceed with care, and perhaps by pruning containers without touching your volumes. – Hugh Esco Jun 01 '22 at 21:22

score 2 · Answer 3 · answered Dec 09 '20 at 10:28

2

It depends how you get up the service, for example use:

docker-compose up -d (on Windows)

instead of docker-compose up. In this way you have the control on terminal to call docker-compose down and the MongoDB process can terminate correctly.

answered Dec 09 '20 at 10:28

capo11

790
3
11
32

This worked for me, but I also had the issue of old data files that I had to delete. – Austin Brown Jan 21 '21 at 16:29
You can issue `docker-compose down` even if you started it wiithout `-d` -- in another terminal window. – Dims Jan 26 '21 at 11:51

score 1 · Answer 4 · answered Oct 10 '21 at 18:31

On a Mac, you might be able to resolve the issue by deleting the /Users/{your account}/data folder.

You should be able to find the folder by going to Finder -> Go -> Go to Folder -> And search ~/Users/.

Other solutions that I tried before this that didn't work:

stopping and removing all mongo containers
removing all mongo images
Clean / Purge data from Docker Desktop
uninstall and reinstall Docker

BenLa · Answer 5 · 2022-09-03T18:20:13.907

1

For me what helped is deleting the mounted host directory, deleting the volume with docker volume rm {CONTAINER NAME\ID}. Make sure to write the volume in compose right, for example:

  ...

  database:
    container_name: database
    image: mongo
    ports:
      - '27017:27017'
    volumes:
      - db:/data/db  
  ...  
  volumes: 
    db:

edited Sep 03 '22 at 18:20

answered Sep 03 '22 at 18:19

BenLa

27
1
6

score 0 · Answer 6 · answered Dec 02 '21 at 10:29

0

Install WSL2 ( It requires recent windows update)
Docker -> Settings -> Enable-> Use WSL 2 based engine

answered Dec 02 '21 at 10:29

Muthukumar R

141
1
7

This does not provide an answer to the question. Once you have sufficient [reputation](https://stackoverflow.com/help/whats-reputation) you will be able to [comment on any post](https://stackoverflow.com/help/privileges/comment); instead, [provide answers that don't require clarification from the asker](https://meta.stackexchange.com/questions/214173/why-do-i-need-50-reputation-to-comment-what-can-i-do-instead). - [From Review](/review/late-answers/30487406) – Dec 03 '21 at 01:30

exit code 14 error in mongodb container, I'm using mongodb container with with volume path then received exit code 14 error

6 Answers6