clue / docker-json-server Goto Github PK

the --route option is not there it would be nice if you add it

I just want to inform you, that the "trusted build on the docker index" (https://index.docker.io/u/clue/json-server/) link within the README.md returns an empty page with tons or errors in the console.

I tried to clone your repository and tried to build docker image.

When I tried to run newly built docker image, Server which is running inside docker container was not accessible from outside.
After more debug i found issue

run.sh needs to be modified with adding host -H 0.0.0.0

Hello,
For some reason I keep getting the error of "Error: Data must be an object." when running through docker, but not if I just start json-server normally through cli.

This is the run.sh I was trying to use

#!/bin/bash

args="$@"

args="$@"
host="-H 0.0.0.0"
port="-p 9004"
dest="http://mysite.com/news/index.json"

json-server $args $port $host $dest

If I just run it like this, it works just fine. :

json-server -p 9004 -H 0.0.0.0 http://mysite.com/news/index.json

Thanks,
-MH

I had an issue when using the default configuration threw a Docker Swarm.
I couldn't access the services becaus json-server was listening only to localhost.

Could you bring -H 0.0.0.0 on the run.sh by default so others won't have the same problem ?

args="$@ -H 0.0.0.0 -p 80"

Empty response being returned from the docker container.

I don't know if this is a problem with the json server in general? I've tried writing my own Dockerfiles before I found this project (just to see if I could get something to work).

Any advise would be appreciated!

I passed the --watch argument.

when db.json file changes in host machine the changes also obviously reflects inside docker container /data/db.json since volume mounted. But it still supplies the old db.json values.

The file is changed Right ?

When Post through curl it works properly. Restarting docker container it works properly.

Changing file directly not working (--watch)

Should be as simple as a file like the following into a file called docker-compose.yml:

json_server:
  build: .
  command: 'sh run.sh'
  working_dir: /data
  ports:
   - '80:80'

Then, perhaps you could later map the volume in via docker-compose instead of via the Dockerfile:

json_server:
  build: .
  command: 'sh run.sh'
  working_dir: /data
  ports:
   - '80:80'
  volumes:
   - ./data:/data

Hi, just a suggestion for the readme.md.
In my setup, the host file db.json was not updated after I added data using the REST API. This was resolved when I mapped the folder containing db.json as volume instead of the file directly. Might be added to the readme.

$ docker run -d -p 80:80 -v /home/user/articles.json:/data/db.json clue/json-server

just exits

Hi.
I run the container with the example json (posts and comments). When I go to the adress: http://localhost:80/posts I get the data but the container crashes. The same if I use curl.

I get the response:

GET /posts 304 16.824 ms - -

/usr/local/lib/node_modules/json-server/node_modules/lowdb/src/disk.js:23
if (err) throw err
^
Error: EBUSY, rename '/data/.~db.json'