I can't get past: 3.4: Pulling from library/mongo

Bruce Gust
Bruce Gust used Ask the Experts™
on
I've got Docker installed and I've downloaded a boilerplate from https://github.com/kunalkapadia/express-mongoose-es6-rest-api

Everything's installed including "yarn" - all good.

But when I run this: $ bash bin/development.sh, which, from what I understand is instantiating the docker dynamic, it just hangs on "3.4: Pulling from library/mongo."

Here's what it looks like:

screenshot
I am poised on the threshold of greatness! I've got my Node syntax proofed and ready! All I've got to do is drop it into the Boilerplate and wrap it in a Docker image and I will be done!

But I can't get past this thing and I'm stuck!

Thoughts?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Most Valuable Expert 2017
Distinguished Expert 2018

Commented:
I tried staring at the image of a hung bash script waiting for inspiration - but I was sorely disappointed (and late for my next meeting)

I am guessing that the secret lies inside development.sh

We would need to see what this is doing and then go from there.
Bruce GustPHP Developer

Author

Commented:
How do we pop the hood on that?

BTW: Julian, I can appreciate being late for one's next meeting. My team is waiting on the piece that I'm supposed to deliver as a microservice and, dude, I've got it done. The Node code is complete and completely sound, but it has to be wrapped up in a specific boilerplate and delivered as a Docker image.

But unless I can figure out this piece that everyone else has had no trouble with, then I'm going to be "late."

That said, I'm brand new to Docker and I'm just following the recipe as it's documented on Boilerplate's webpage which you can access by heading out to https://github.com/kunalkapadia/express-mongoose-es6-rest-api (look under Getting Started / Docker).

Anything that you smell, see, sense - let me know, Julian. Everyone on my team is just looking at me with their teeth in their mouth having no idea why my computer is struggling and their's is pristine.

Bring it!
Most Valuable Expert 2017
Distinguished Expert 2018

Commented:
I can appreciate being late for one's next meeting
In this case it was an attempt at (maybe a bit too) dry humour - they sometimes let me go outside every two weeks to see the birds and things - for the rest I am shackled to my desk

My point was, in that /bin folder there should be a script (development.sh) - whatever is inside it will help tell us where it is getting stuck.

I am assuming you have given it the wait-and-see treatment?
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Bruce GustPHP Developer

Author

Commented:
Well, I want to be more aggressive then "wait and see." I really need to figure this out...

Julian, do you smell that? That's the aroma of a completely project, I've just got to get past this one "thing!"

Here's the "development.sh" script:

#!/usr/bin/env bash

# --build: Build images before starting containers.
# --abort-on-container-exit: Stops all containers if any container is stopped
docker-compose up --build --abort-on-container-exit

I know, right? Not a whole lot...

What do you think?
Bruce GustPHP Developer

Author

Commented:
Julian!

Hold the phone!

Whether I meant to do it or not, I let that command stew over night. In addition, I had some alerts come up on my system saying that I was running out of space, so perhaps deleting and backing up some files made a difference, I don't know.

But I'm seeing something different now. Here's the error I'm getting presently (and I'm giving you the whole readout in case there's something that's relevant to where the script is stopping now...):

$ bash bin/development.sh
Building express-mongoose-es6-rest-api
Step 1/9 : FROM node:8.10.0
8.10.0: Pulling from library/node
Service 'express-mongoose-es6-rest-api' failed to build: no matching manifest for windows/amd64 10.0.        
18362 in the manifest list entries


What I having bold is the stopping point now...
Most Valuable Expert 2017
Distinguished Expert 2018

Commented:
Well, I want to be more aggressive then "wait and see." I really need to figure this out...
No, I mean wait and see if the script completes - i.e. it might just be taking a long time.
Most Valuable Expert 2017
Distinguished Expert 2018

Commented:
I know, right? Not a whole lot...
Ok that is building a docker container - it might take some time.

Comes back to how long did you wait for it to complete?
Most Valuable Expert 2017
Distinguished Expert 2018
Commented:
There is a discussion here https://stackoverflow.com/questions/48066994/docker-no-matching-manifest-for-windows-amd64-in-the-manifest-list-entries that points to building a specific type of container - it looks like you might need to change that.
Bruce GustPHP Developer

Author

Commented:
The last thread you referenced made the difference!

I've got another issue now, though! I'll close this one before I put that on the boards!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial