You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running Ubuntu 20.04.6 LTS on an Azure Lab Services VM. I've downloaded hbase-docker. I run:
sudo docker build -t dajobe/hbase .
And I'm getting this:
14.22 curl: (77) error setting certificate verify locations:
14.22 CAfile: /etc/ssl/certs/ca-certificates.crt
14.22 CApath: /etc/ssl/certs
14.22
14.22 gzip: stdin: unexpected end of file
14.23 tar: Child returned status 1
14.23 tar: Error is not recoverable: exiting now
------
Dockerfile:14
--------------------
13 |
14 | >>> RUN /build/prepare-hbase.sh && \
15 | >>> cd /opt/hbase && /build/build-hbase.sh \
16 | >>> cd / && /build/cleanup-hbase.sh && rm -rf /build
17 |
--------------------
ERROR: failed to solve: process "/bin/sh -c /build/prepare-hbase.sh && cd /opt/hbase && /build/build-hbase.sh cd / && /build/cleanup-hbase.sh && rm -rf /build" did not complete successfully: exit code: 2
I'm doing this for a class. What's interesting is that this had been working for my classmates up until some time in late February or early March, and then whatever the date was, those who tried it after that started seeing this same problem. My classmates have the same setup with their own VMs.
I've inspected the ca-certificates.crt file and the certs directory, and I see nothing untoward in terms of permissions or contents.
If anyone has any idea what's going on, I'd appreciate it. It would be helpful even just to be able to reproduce the problem with the constituent simple commands outside the context of the docker command.
The text was updated successfully, but these errors were encountered:
I'm running Ubuntu 20.04.6 LTS on an Azure Lab Services VM. I've downloaded hbase-docker. I run:
And I'm getting this:
I'm doing this for a class. What's interesting is that this had been working for my classmates up until some time in late February or early March, and then whatever the date was, those who tried it after that started seeing this same problem. My classmates have the same setup with their own VMs.
I've inspected the
ca-certificates.crt
file and thecerts
directory, and I see nothing untoward in terms of permissions or contents.If anyone has any idea what's going on, I'd appreciate it. It would be helpful even just to be able to reproduce the problem with the constituent simple commands outside the context of the docker command.
The text was updated successfully, but these errors were encountered: