Use new mongo image for tutorial - fixes 383 #476
Conversation
use smaller clusterhq mongo image
|
You'll need to update the references to |
|
Well it certainly reduces the size of the VMs... |
|
But when I substitute the new image name into the tutorial application YAML files, the application fails to load. See below: (master)[richard@drax flocker-tutorial]$ ssh root@172.16.255.250 gear status mongodb-example
ctr-mongodb-example.service - Container mongodb-example
Loaded: loaded (/var/lib/containers/units/mo/ctr-mongodb-example.service; enabled)
Active: failed (Result: exit-code) since Thu 2014-08-07 04:53:21 PDT; 37s ago
Process: 26523 ExecStartPre=/bin/sh -c /usr/bin/docker inspect --format="Reusing {{.ID}}" "mongodb-example-data" || exec docker run --name "mongodb-example-data" --volumes-from "mongodb-example-data" --entrypoint /bin/true "clusterhq/mongdb:latest" (code=exited, status=1/FAILURE)
Aug 07 04:53:20 node1 systemd[1]: Starting Container mongodb-example...
Aug 07 04:53:20 node1 sh[26523]: Error: No such image or container: mongodb-example-data
Aug 07 04:53:20 node1 sh[26523]: Unable to find image 'clusterhq/mongdb:latest' locally
Aug 07 04:53:20 node1 sh[26523]: Pulling repository clusterhq/mongdb
Aug 07 04:53:21 node1 sh[26523]: 2014/08/07 04:53:21 HTTP code: 404
Aug 07 04:53:21 node1 systemd[1]: ctr-mongodb-example.service: control process exited, code=exited status=1
Aug 07 04:53:21 node1 systemd[1]: Failed to start Container mongodb-example.
Aug 07 04:53:21 node1 systemd[1]: Unit ctr-mongodb-example.service entered failed state.
container_status: Unable to fetch container status logs: exit status 3 |
|
@wallrj I think you made a typo in your substitutions :)
"mongdb" should be "mongodb" |
|
Ah ok. That was a silly mistake. But I've now found what I think is a real problem... |
|
Make sure you start mongod with |
|
Have now added |
| @@ -1,7 +1,7 @@ | |||
| "version": 1 | |||
| "applications": | |||
| "mongodb-volume-example": | |||
| "image": "mongodb-tutorial" | |||
| "image": "clusterhq/mongodb" | |||
| "ports": | |||
| - "internal": 27017 | |||
| "external": 27017 | |||
There was a problem hiding this comment.
You also need to change the mount point to be /data/db rather than /data.
modified: tutorial/volume-application.yml
itamarst
changed the title
|
Thanks for getting this done! The new image works... except that when Please rebuild the image with a stable version of MongoDB and then merge this. |
|
@itamarst I had to use the cutting-edge nightly to get it to work with the buildroot/busybox image; in stable 2.6, every time I connected to the |
…/flocker into mongo-tutorial-vagrantfile-383
|
Can we suppress the warning some other way, e.g. is there a command line option on server or can we patch it or something? |
|
There's no command line option I can find documented. Really, is there anything wrong with just including a bit of text in the tutorial that says something like "To keep your downloads for the tutorial as speedy as possible, we've bundled the latest dev version of MongoDB in to a micro-sized Docker image. You should not use this for production; instead use the canonical trusted Docker MongoDB build." |
|
That sounds fine. Put that in and merge - thank you! |
Explain that we're using dev version of mongo
Use new mongo image for tutorial - fixes 383
use smaller clusterhq mongo image
we have a lightweight mongo image now deployed to the public docker index.
Part of #383 - need to checkout this branch and see if the tutorial is still successful when run with this Vagrantfile.