• Register
0 votes
598 views

Problem :

While installing a docker project from github facing following issue
package context: unrecognized import path "context" (import path does not begin with hostname)
6 5 3
6,930 points

Please log in or register to answer this question.

1 Answer

0 votes

Solution :

This package context is only available in go versions 1.7 and after you try to check all the dockerfiles in your specified folders e.g. microservices-docker-go-mongodb-master in your link and change 

from golang:1.6 to golang:1.7

Next you need to change the port number of the db in your file docker-compose.yml

e.g.

from

image: mongo:3.3
container_name: cinema-db
ports:
  - "27017:27017"
volumes:
  - ./backup:/backup:rw 

to

ports:
- "27018:27018"

As you have already installed mongodb 27017 you must change it.

9 7 4
38,600 points

Related questions

0 votes
1 answer 12 views
12 views
Problem: I'm installing a docker project from github and there are commands given in the repository and I'm just following them. The project is almost download but it gives an error while downloading the RUN go get github.com/gorilla/mux In my system I have ... context: unrecognized import path "context" (import path does not begin with hostname) Can any one please tell how this error be solved.
asked Apr 24 ochena 23.3k points
0 votes
1 answer 14 views
14 views
Problem: x509: certificate signed by unknown authority.
asked Mar 3 Dan phillip 4.8k points
0 votes
1 answer 7 views
7 views
Problem: Hi i have an issue that iunable to prepare context: unable to evaluate symlinks in dockerfile path.
asked Mar 18 waseem memon 2.4k points
0 votes
1 answer 4 views
4 views
Problem: Has anyone faced this before? > Error response from daemon: no build stage in current context
asked 3 days ago Priscilla Gurpreet 3.7k points
0 votes
1 answer 3 views
3 views
Problem: Please can anyone tell me the right procedure to do it? unable to locate package cuda-command-line-tools
asked Apr 18 Ifra 37.2k points
0 votes
1 answer 10 views
10 views
Problem: When I try to build the image again (it doesn't work, 137 error as expected), I still get the same error when I try to access the logs: Error response from daemon: configured logging driver does not support reading When I try to inspect the logging driver the ... .LogConfig.Type}}' 3016507bd1dc I get none back. Does anyone what I'm missing or how I can get the logs of the failed build?
asked May 2 Humaira ahmed 50.7k points
0 votes
1 answer 2 views
2 views
Problem: "Docker "is a buzz word these days and I am trying to figure out, what it is and how does it work. And more specifically, how is it different from the normal VM, I need information about this facts.
asked Apr 30 salim1 60.6k points
0 votes
1 answer 10 views
10 views
Problem: I have multiple SQL Server instance and I want to start service automatically for each when system starts. So I choose services state to automatically but it does not start automatically. Here is the error log of one of the SQL Server instances 2018-07-12 17:55: ... computer logon user's account but it does not work. I am not sure why this error occurs and I cant find any useful resource.
asked May 4 jamuna1 30.2k points
0 votes
1 answer 5 views
5 views
Problem: I am a newbie to docker. When I go through docker tutorial, I saw that "Docker client can communicate with more than one daemon". What does that mean exactly?
asked May 3 sumaiya simi 43.9k points