Docker容器内mongoimport导入JSON至MongoDB失败，求解决方案

Hey there, let’s work through why your mongoimport command is failing—this is a super common issue when working with Dockerized MongoDB, and I’ve fixed this exact problem more times than I can count. Let’s break down the most likely causes and fixes:

1. The JSON file isn’t accessible inside the container #

When you jump into the container with docker exec, files on your host machine don’t magically appear inside the container. You’ve got two solid ways to fix this:

• Copy the file into the container first
  Exit the container (or open a new terminal window) and run this command to copy your local JSON file into the container:

  docker cp /path/to/your/local/xxx.json <My-Name>:/tmp/xxx.json
  

  Then go back into the container and use the internal path in your import command:

  mongoimport -d <db-name> -c <c-name> --file /tmp/xxx.json
  

• Mount a host directory as a volume (better for repeated imports)
  If you plan to import files regularly, restart your MongoDB container with a volume mount that links a local folder to the container:

  docker stop <My-Name>
  docker run -d -v /path/to/your/local/files:/container/files --name <My-Name> mongo
  

  Now your local files are accessible at /container/files inside the container—no more copying files back and forth.

2. Syntax mistakes in the mongoimport command #

Double-check these easy-to-miss syntax issues:

• JSON format mismatch: If your file is a single array of documents (like [{...}, {...}]), you need the --jsonArray flag. If each line is a separate document (JSON Lines format), skip the flag. Mixing these up is the #1 cause of parsing errors:
  • For array-formatted JSON: mongoimport -d <db-name> -c <c-name> --jsonArray --file xxx.json
  • For line-separated JSON: mongoimport -d <db-name> -c <c-name> --file xxx.json
• Typos in database/collection names: MongoDB will create the database and collection if they don’t exist, so a typo might mean you’re importing into a non-existent (and unintended) location.
• Missing authentication flags: If your MongoDB instance requires credentials, add these to the command:

  mongoimport -d <db-name> -c <c-name> --file xxx.json -u <your-username> -p <your-password> --authenticationDatabase admin
  

3. Permission issues inside the container #

If you copied the file into the container, the mongodb user (which runs the database service) might not have read access to it. Fix this by setting the correct permissions:

chown mongodb:mongodb /tmp/xxx.json

Or, since you’re probably running as root inside the container (from docker exec -it), you can just run mongoimport directly without changing permissions.

4. Check the error message! #

This is the step most people skip, but it’s the most helpful. When mongoimport fails, it prints a specific error that tells you exactly what’s wrong:

• Failed: open xxx.json: no such file or directory → File path is incorrect
• Failed: error parsing json: invalid JSON input → Your JSON file has syntax errors (use a validator like jq to check it)
• Failed: authentication failed → You need to add authentication flags to the command

If you still hit a wall, share the exact error message, and we can narrow it down further.

内容的提问来源于stack exchange，提问作者Chars Davy