{"action":"closed","issue":{"url":"https://api.github.com/repos/kwk/docker-registry-frontend/issues/52","labels_url":"https://api.github.com/repos/kwk/docker-registry-frontend/issues/52/labels{/name}","comments_url":"https://api.github.com/repos/kwk/docker-registry-frontend/issues/52/comments","events_url":"https://api.github.com/repos/kwk/docker-registry-frontend/issues/52/events","html_url":"https://github.com/kwk/docker-registry-frontend/issues/52","id":87805954,"number":52,"title":"Setting up development environment questions","user":{"login":"DanielKerrigan","id":8934668,"avatar_url":"https://avatars.githubusercontent.com/u/8934668?v=3","gravatar_id":"","url":"https://api.github.com/users/DanielKerrigan","html_url":"https://github.com/DanielKerrigan","followers_url":"https://api.github.com/users/DanielKerrigan/followers","following_url":"https://api.github.com/users/DanielKerrigan/following{/other_user}","gists_url":"https://api.github.com/users/DanielKerrigan/gists{/gist_id}","starred_url":"https://api.github.com/users/DanielKerrigan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DanielKerrigan/subscriptions","organizations_url":"https://api.github.com/users/DanielKerrigan/orgs","repos_url":"https://api.github.com/users/DanielKerrigan/repos","events_url":"https://api.github.com/users/DanielKerrigan/events{/privacy}","received_events_url":"https://api.github.com/users/DanielKerrigan/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-12T18:01:14Z","updated_at":"2015-06-15T13:31:59Z","closed_at":"2015-06-15T13:31:59Z","body":"Hi, I am running into issues setting up my development environment. The problems occur when running \"docker-compose -f docker-registry-frontend/develop/docker-compose.yml up -d\". First, I receive the following:\r\n>Get:91 http://archive.ubuntu.com/ubuntu/ trusty/universe npm all 1.3.10~dfsg-1 [442 kB]\r\n>debconf: unable to initialize frontend: Dialog\r\n>debconf: (TERM is not set, so the dialog frontend is not usable.)\r\n>debconf: falling back to frontend: Readline\r\n>debconf: unable to initialize frontend: Readline\r\n>debconf: (This frontend requires a controlling tty.)\r\n>debconf: falling back to frontend: Teletype\r\n>dpkg-preconfigure: unable to re-open stdin:\r\n>Fetched 17.0 MB in 7s (2247 kB/s)</code>\r\n\r\nThis occurs once more later on. From what I have Googled, this issue is fixed by adding\r\n\"ENV DEBIAN_FRONTEND noninteractive\" to the Dockerfile. However, both the Dockerfile in /docker-frontend-registry and in the develop folder already contain\r\n>RUN apt-get -y update && \\\r\n>export DEBIAN_FRONTEND=noninteractive\r\n\r\n, which as far as I know should do the same thing.\r\n\r\nThe develop_frontend_1 container exits with a status of 1 shortly after it is created. I ran \"docker logs develop_frontend_1\" to try to see what was happening. I noticed a couple of things:\r\nThe problems seem to begin after the \"node_modules/bower/bin/bower install --allow-root\" command. Everything that happens after that has a form similar to this:\r\n>frontend_1 | bower json3#~3.3.1          not-cached git://github.com/bestiejs/json3.git#~3.3.1\r\n>frontend_1 | bower json3#~3.3.1             resolve git://github.com/bestiejs/json3.git#~3.3.1\r\n\r\nThe container exits with the following:\r\n\r\n>frontend_1 | bower angular-resource#~1.3.0                    ECMDERR Failed to execute \"git ls->remote --tags --heads git://github.com/angular/bower-angular-resource.git\", exit code of #128\r\n>frontend_1 |\r\n>frontend_1 | Additional error details:\r\n>frontend_1 | fatal: unable to access 'https://github.com/angular/bower-angular-resource.git/': Problem with the SSL CA cert (path? access rights?)\r\n>develop_frontend_1 exited with code 1\r\n\r\nSome people solved these problems with \"git config --global url.\"https://\".insteadOf git://\", however this too is already in the Dockerfiles, so I'm not sure why it is still using git://. \r\nAs for the \"Problem with the SSL CA cert (path? access rights?)\", I tried \"yum reinstall openssl ca-certificates -y\" and adding corporate certificates to the Dockerfile to no avail. Interestingly, that command does not always fail to execute for the same link. I also tried to add \r\n>git config --global http.proxy http://USER:PASSWORD@PROXYSERVER:PORT\r\n\r\nwhich resulted in \r\n>fatal: unable to access 'https://github.com/bestiejs/json3.git/': Received HTTP code 404 from proxy after CONNECT\r\n\r\nI am not sure if these issues are interrelated or not. Do you have any suggestions?\r\nThanks for the help,\r\nDan\r\n"}}