I'm trying to install this on ubuntu 16.04 LTS.
bash docker/scripts/install_docker.sh
docker ps
So far, they went fine.
However, "bash docker/scripts/dev_start.sh" resulted in
~/apollo/apollo-master$ bash docker/scripts/dev_start.sh
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Error response from daemon: No such container: apollo_dev
Error response from daemon: No such container: apollo_dev
mknod: /dev/can0: File exists
/home/kyuil75lee/sait/apollo/apollo-master/data/core/core_%e.%p
[WARNING] Failed to find device with pattern "ttyUSB*" ...
[ OK ] Found device: /dev/ttyS31.
[ OK ] Found device: /dev/ttyS30.
[ OK ] Found device: /dev/ttyS29.
[ OK ] Found device: /dev/ttyS28.
[ OK ] Found device: /dev/ttyS27.
[ OK ] Found device: /dev/ttyS26.
[ OK ] Found device: /dev/ttyS25.
[ OK ] Found device: /dev/ttyS24.
[ OK ] Found device: /dev/ttyS23.
[ OK ] Found device: /dev/ttyS22.
[ OK ] Found device: /dev/ttyS21.
[ OK ] Found device: /dev/ttyS20.
[ OK ] Found device: /dev/ttyS19.
[ OK ] Found device: /dev/ttyS18.
[ OK ] Found device: /dev/ttyS17.
[ OK ] Found device: /dev/ttyS16.
[ OK ] Found device: /dev/ttyS15.
[ OK ] Found device: /dev/ttyS14.
[ OK ] Found device: /dev/ttyS13.
[ OK ] Found device: /dev/ttyS12.
[ OK ] Found device: /dev/ttyS11.
[ OK ] Found device: /dev/ttyS10.
[ OK ] Found device: /dev/ttyS9.
[ OK ] Found device: /dev/ttyS8.
[ OK ] Found device: /dev/ttyS7.
[ OK ] Found device: /dev/ttyS6.
[ OK ] Found device: /dev/ttyS5.
[ OK ] Found device: /dev/ttyS4.
[ OK ] Found device: /dev/ttyS3.
[ OK ] Found device: /dev/ttyS2.
[ OK ] Found device: /dev/ttyS1.
[ OK ] Found device: /dev/ttyS0.
[ OK ] Found device: /dev/can0.
[ OK ] Found device: /dev/ram15.
[ OK ] Found device: /dev/ram14.
[ OK ] Found device: /dev/ram13.
[ OK ] Found device: /dev/ram12.
[ OK ] Found device: /dev/ram11.
[ OK ] Found device: /dev/ram10.
[ OK ] Found device: /dev/ram9.
[ OK ] Found device: /dev/ram8.
[ OK ] Found device: /dev/ram7.
[ OK ] Found device: /dev/ram6.
[ OK ] Found device: /dev/ram5.
[ OK ] Found device: /dev/ram4.
[ OK ] Found device: /dev/ram3.
[ OK ] Found device: /dev/ram2.
[ OK ] Found device: /dev/ram1.
[ OK ] Found device: /dev/ram0.
[ OK ] Found device: /dev/loop7.
[ OK ] Found device: /dev/loop6.
[ OK ] Found device: /dev/loop5.
[ OK ] Found device: /dev/loop4.
[ OK ] Found device: /dev/loop3.
[ OK ] Found device: /dev/loop2.
[ OK ] Found device: /dev/loop1.
[ OK ] Found device: /dev/loop0.
[ OK ] Found device: /dev/loop-control.
Unable to find image 'apolloauto/apollo:dev-latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
Error response from daemon: No such container: apollo_dev
Please advise me how to correct these problems.
Thank you.
It seems that maybe your network problem, you can try more or ping the docker.io's domain first. Good Luck!
Oh I set up the HTTPS_PROXY to resolve the above issue.
However, when doing "bash apollo.build" (so far so fine),
I encountered the following errors:
kyuil75lee@in_dev_docker:/apollo$ bash apollo.sh build
System check passed. Build continue ...
[WARNING] ESD CAN library supplied by ESD Electronics does not exist.
[WARNING] If you need ESD CAN, please refer to third_party/can_card_library/esd_can/README.md
Start building, please wait ...
Warning: ignoring http_proxy in environment.
.
____Loading package:
____Loading package: @google_styleguide//
____Loading package: @com_github_google_protobuf//
____Loading package: @curlpp//
____Loading package: @glog//
____Loading package: @gtest//
____Loading package: @com_github_grpc_grpc//
____Failed to connect to https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz trying again in 100ms
____Failed to connect to https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz trying again in 200ms
____Failed to connect to https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz trying again in 400ms
____Failed to connect to https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz trying again in 800ms
^C
kyuil75lee@in_dev_docker:/apollo$
Bazel caught interrupt signal; shutting down.
____Failed to connect to https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz trying again in 1,600ms
ERROR: query interrupted.
Java or Bazel set-up problem?
Please advise me again.
Thank you.
Same connection problem. Basically bazel tried to download https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz and it can't reach from your connection.
It worked fine for the previous ones (in WORKSPACE), for example,
new_http_archive(
name = "curlpp",
url = "https://github.com/jpbarrette/curlpp/archive/v0.8.1.tar.gz",
sha256 = "97e3819bdcffc3e4047b6ac57ca14e04af85380bd93afe314bee9dd5c7f46a0a",
build_file = "third_party/curlpp.BUILD",
strip_prefix = "curlpp-0.8.1",
)
However, this is where I failed.
new_http_archive(
name = "ros",
url = "https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz",
build_file = "third_party/ros.BUILD",
strip_prefix = "ros",
)
There is no "sha256" for ros/apolloauto,
so I think SSL connection/certificate problem happened here.
I don't understand why "https://github.com/jpbarrette/curlpp/archive/v0.8.1.tar.gz" is reachable
but "https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz" is unreachable.
Both can be downloaded from web-browser...
I can download it manually.
Any idea how to cure this?
Thank you.
https://docs.bazel.build/versions/master/be/workspace.html#new_http_archive
sha256 is optional. It won't cause SSL certification failure. It is used to verify tar content not for SSL.
The network connection problem is still the reason for the failure. Does this work for you?
wget https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz
Yeah, wget is working...
$ wget https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz
--2017-07-07 14:44:10-- https://github.com/ApolloAuto/apollo-platform/releases/download/1.0.0/ros-indigo-apollo-1.0.0.x86_64.tar.gz
Connecting to 75.12.251.5:8080... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/95915580/8c73f32a-60d4-11e7-977c-7b194abf6427?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20170707%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170707T054253Z&X-Amz-Expires=300&X-Amz-Signature=dc088f5d205c1d9cdbb310e8db8108a1a3f3653a3e7f4f886a222d6659e9508c&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dros-indigo-apollo-1.0.0.x86_64.tar.gz&response-content-type=application%2Foctet-stream [following]
--2017-07-07 14:44:11-- https://github-production-release-asset-2e65be.s3.amazonaws.com/95915580/8c73f32a-60d4-11e7-977c-7b194abf6427?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20170707%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170707T054253Z&X-Amz-Expires=300&X-Amz-Signature=dc088f5d205c1d9cdbb310e8db8108a1a3f3653a3e7f4f886a222d6659e9508c&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dros-indigo-apollo-1.0.0.x86_64.tar.gz&response-content-type=application%2Foctet-stream
Connecting to 75.12.251.5:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 14088416 (13M) [application/octet-stream]
Saving to: ‘ros-indigo-apollo-1.0.0.x86_64.tar.gz’
o-1.0.0.x86_64.tar.gz 14%[======> ] 1.93M 313KB/s eta 41s
It seems wget knows your proxy setting but bazel doesn't pick up your proxy setting.
# bazel
Warning: ignoring http_proxy in environment.
# wget
Proxy request sent,
One related discussion is at https://github.com/bazelbuild/bazel/issues/587
In short, bazel looks for either HTTP_PROXY or HTTPS_PROXY env variables.
我的执行安装时也出现了这样的错误,看了你们的解决方案,还是没有解决,把下载好的 ros-indigo-apollo-1.0.0.x86_64.tar.gz放到哪个目录里呢?谢谢你,我不是很了解。这是我的安装错误日志,到了这一步,又卡住了。
ai@ying ~/Documents/book/git/apollo $ bash docker/scripts/dev_start.sh
Error response from daemon: Get https://registry-1.docker.io/v2/: read tcp 192.168.30.195:60524->52.44.30.97:443: read: connection reset by peer
Error response from daemon: No such container: apollo_dev
Error response from daemon: No such container: apollo_dev
mknod: /dev/can0: File exists
/home/ai/Documents/book/git/apollo/data/core/core_%e.%p
[WARNING] Failed to find device with pattern "ttyUSB*" ...
[ OK ] Found device: /dev/ttyS31.
[ OK ] Found device: /dev/ttyS30.
[ OK ] Found device: /dev/ttyS29.
[ OK ] Found device: /dev/ttyS28.
[ OK ] Found device: /dev/ttyS27.
[ OK ] Found device: /dev/ttyS26.
[ OK ] Found device: /dev/ttyS25.
[ OK ] Found device: /dev/ttyS24.
[ OK ] Found device: /dev/ttyS23.
[ OK ] Found device: /dev/ttyS22.
[ OK ] Found device: /dev/ttyS21.
[ OK ] Found device: /dev/ttyS20.
[ OK ] Found device: /dev/ttyS19.
[ OK ] Found device: /dev/ttyS18.
[ OK ] Found device: /dev/ttyS17.
[ OK ] Found device: /dev/ttyS16.
[ OK ] Found device: /dev/ttyS15.
[ OK ] Found device: /dev/ttyS14.
[ OK ] Found device: /dev/ttyS13.
[ OK ] Found device: /dev/ttyS12.
[ OK ] Found device: /dev/ttyS11.
[ OK ] Found device: /dev/ttyS10.
[ OK ] Found device: /dev/ttyS9.
[ OK ] Found device: /dev/ttyS8.
[ OK ] Found device: /dev/ttyS7.
[ OK ] Found device: /dev/ttyS6.
[ OK ] Found device: /dev/ttyS5.
[ OK ] Found device: /dev/ttyS4.
[ OK ] Found device: /dev/ttyS3.
[ OK ] Found device: /dev/ttyS2.
[ OK ] Found device: /dev/ttyS1.
[ OK ] Found device: /dev/ttyS0.
[ OK ] Found device: /dev/can0.
[WARNING] Failed to find device with pattern "ram*" ...
[ OK ] Found device: /dev/loop7.
[ OK ] Found device: /dev/loop6.
[ OK ] Found device: /dev/loop5.
[ OK ] Found device: /dev/loop4.
[ OK ] Found device: /dev/loop3.
[ OK ] Found device: /dev/loop2.
[ OK ] Found device: /dev/loop1.
[ OK ] Found device: /dev/loop0.
[ OK ] Found device: /dev/loop-control.
Unable to find image 'apolloauto/apollo:dev-20170707_1129' locally
dev-20170707_1129: Pulling from apolloauto/apollo
cb56c90f0b30: Pulling fs layer
0acc551e5716: Pulling fs layer
8956dcd35143: Pulling fs layer
908242721214: Pulling fs layer
b44ff14dd3bb: Pulling fs layer
68a565a88d05: Pulling fs layer
84198a14886c: Pulling fs layer
d4b61997bf6f: Pulling fs layer
fad90c9e6967: Pulling fs layer
c3a71b8081c8: Pulling fs layer
1b6b7f5fd058: Pulling fs layer
59564810fdd3: Pulling fs layer
c3cf6685d4cd: Pulling fs layer
8ce4073e8bb7: Pulling fs layer
fb888a093cc0: Pulling fs layer
1b6b7f5fd058: Download complete
7b7fe4477995: Download complete
89a17d68e3e2: Download complete
e274af5eb115: Download complete
cd580452c88c: Download complete
f5499142713f: Download complete
08ef9610a2f5: Download complete
46e28973d034: Download complete
276ce7aafce3: Download complete
b9a2230796d7: Download complete
d125bdde2f39: Download complete
598a4b6f9275: Download complete
29c4a1ccdc5b: Download complete
1022ce674994: Download complete
aa9329b7dd1e: Download complete
0a464d8cb669: Download complete
587566f9fa9a: Download complete
57d7ecae556d: Download complete
ec7992419a91: Download complete
65a09c54e731: Download complete
e2f3689560f1: Download complete
419b3e44ef6d: Download complete
505679240dc6: Download complete
docker: read tcp 192.168.30.195:52288->13.32.230.203:443: read: connection reset by peer.
See 'docker run --help'.
Error response from daemon: No such container: apollo_dev
ai@ying ~/Documents/book/git/apollo $ docker run -d apollo_dev
Unable to find image 'apollo_dev:latest' locally
docker: Error response from daemon: repository apollo_dev not found: does not exist or no pull access.
See 'docker run --help'
@AI-Ying It looks your env doesn't set up docker correctly. Does docker ps work for you?
docker ps does work as follows
ai@ying 09:39:54 $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
@AI-Ying From your error msg, it seems your network connection need setup proxy. Have you set up the proxy variable? Thanks.
Error response from daemon: Get https://registry-1.docker.io/v2/: read tcp 192.168.30.195:60524->52.44.30.97:443: read: connection reset by peer
ok, I got it. Thank you very much!