qvantel / orcd

An operational dashboard visualizing worldwide roaming usage and and product usage from generated fake CDR events
MIT License
8 stars 0 forks source link

Error when runnning containers.sh #6

Closed Lillfilly closed 7 years ago

Lillfilly commented 7 years ago

Running the containers.sh script seems to mostly work, I am however getting the following errors when executing it.

[error] Not a valid command: assembly [error] Not a valid key: assembly [error] assembly [error] ^ Error response from daemon: No such image: backend:latest unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/student/Qvantel/Qvantel/QvantelBackend/Dockerfile: no such file or directory Unable to find image 'backend:latest' locally Pulling repository docker.io/library/backend docker: Error: image library/backend:latest not found.

Max-Meldrum commented 7 years ago

Tried running the script on Martin's computer but had problems accessing a tar.gz file from inside the container that was built. Lets look at it tomorrow.

johan-bjareholt commented 7 years ago

/Qvantel/Qvantel/QvantelBackend/Dockerfile: no such file or directory

@Lillfilly Since the Docker file is not present you do most likely not have the latest version of QvantelBackend. Since you also had issues with pullall.sh that is very likely. Configure the git repos by either setting up the origin to https with the configure_ssh_https.sh script or manually change it to https and then either run pullall.sh again or manually git pull in the QvantelBackend repository.

@Max-Meldrum What tar.gz file? I am not aware of any tar.gz files.

Max-Meldrum commented 7 years ago

@johan-bjareholt

When the container is being built, it tries to fetch some tar.gz from the net and it was not able to get it, so it ended in the build falling.

Max-Meldrum commented 7 years ago

the sbt assembly plugin and the dockerfile is not present in the backend repo. Try the pullall script and with https and try again.

Regarding the problem with the container not reaching the internet, run the telenor_wifi_docker_dns script and then the backend image should be built without any problem.

johan-bjareholt commented 7 years ago

Is this still a issue?

Lillfilly commented 7 years ago

Just tried both the start & stop commands. Seems to be working fine now!