I tried to install dvdcli on my mesos master.
I typed the following line in the console. But I get forbidden error.
I even tried to do a direct download. Still I get forbidden error.
curl -sSL https://dl.bintray.com/emccode/dvdcli/install | sh -s stable
Can someone help?
Its not just you https://github.com/rexray/dvdcli/issues/37. That was posted back in June and its still unresolved.
Also Dell is no longer funding the open source Code Team initiative https://blog.thecodeteam.com/2018/02/22/final-thank-code-team/ so I'm not sure about the future of the project. I have not been following it closely. I would suggest reaching out to on https://github.com/rexray/dvdcli/issues/37. Hopefully someone will have an answer for you there
Related
I'm learning about blockchain and now I'm starting with Sawtooth network as I have heard that it's quite popular. I came across and research paper about CoopEdge and it's very interesting (github link: https://github.com/coopedge/prototype).
However, I don't know clearly how to make this work. I personally send an email and still don't have the response so I have to try it with basic knowledge (blindly, somehow). There are two folder sawtooth-core and sawtooth-poer. I went with poer because the publication was talking about it. There are two type of dockerfile - docker-compose.yml and docker-compose-installed.yaml. I installed the first one with docker-compose and there was no problem. However, when I tried to install the latter one I keep getting the error:
Step 9/13 : RUN export VERSION=$(./bin/get_version) && sed -i -e "0,/version.*$/ s/version.*$/version\ =\ \"${VERSION}\"/" Cargo.toml && /root/.cargo/bin/cargo deb --deb-version $VERSION
---> Running in 7d244fc29e30
/bin/sh: 1: ./bin/get_version: Permission denied
91mcargo-deb: Argument to option 'deb-version' missing
I tried several methods by searching the internet but no luck so far. I also tried to install with root (sudo -i) but still it doesn't work at all.
Another thing is I don't know the second docker-file is mandatory for installation as there is no document or guidance provided by the author.
I appreciate any help that could solve this permission problem. Thank so much.
P.s: I'm using virtual machine with Ubuntu 18.04.
I tried to follow the instruction from Docker EE instruction.
https://docs.docker.com/ee/docker-ee/ubuntu/#set-up-the-repository
I met the problem with step five: Add Docker’s official GPG key using your customer Docker Engine - Enterprise repository URL.
curl -fsSL "${DOCKER_EE_URL}/ubuntu/gpg" | sudo apt-key add -
When I type this command, terminal returned
curl: (22) The requested URL returned error: 403
gpg: no valid OpenPGP data found.
I tried to use the browser open the url of "${DOCKER_EE_URL}/ubuntu/gpg", it also returns 403.
Then, I thought maybe my local environment is not clean, so I rent server from DigitalOcean, but it still returned the same message.
Could someone, please point me into the right direction? Thank you!
Update: I tried to use centos, it can't work, either.
I had the same issues this morning. For me the issue is now resolved.
Looks like it takes a couple of hours before the key is available (after requesting a trial license).
I am using launcher.gcr.io/google/jenkins2 to run jenkins in gcp kubernetes engine.
Everything seems ok except that I get Could not initialize class org.jfree.chart.JFreeChart error for every chart that jenkins attempt to draw. I googled the error and almost everyone solves that with adding -Djava.awt.headless=true. As you can guess I already tried that and it does not work.
Ideas?
One other possible solution/workaround is seen in JENKINS issue 39636:
I installed libxext6 libxrender1 fontconfig libfontconfig but it didn't help. After that I also installed libjfreechart-java but I still have the same problem.
Commenting out the assistive_technologies line in /etc/java-8-openjdk/accessibility.properties solved it.
You can see that recommendation in tianon's comment of that answer:
In my case it ended up being bugs.debian.org/798794 (from "Assistive technology not found error while building aprof-plot").
Adding "RUN sed -i 's/^assistive_technologies=/#&/' /etc/java-8-openjdk/accessibility.properties" to my Dockerfile fixed it. :)
A little confused at the moment. I've got docker on one my servers and as it doesn't have internet access, I'm trying to build a base image for centos7.4. The nice Docker site has a mkimage_yum.sh script for this purpose, but it consistently fails when it tries running:
yum -c /tmp/mkimage_yum.sh.gnagTv/etc/yum.conf --installroot=/tmp/mkimage_yum.sh.gnagTv -y clean all
with a "No enabled repos" error. The thing is, if I enter "yum repolist" I get back 17 entries, and I have manually tried to set several repos to enabled. Yet, this command still fails, and I do not understand what could be missing.
Anybody have some idea of what I can so this succeeds?
Jay
I figured out why this was failing, the docker file for mkimage_yum.sh does not contain the proper code if you're storing your repos in /etc/yum.repos.d, it assumes that everything is in /etc/yum.conf. This is really not correct, and it causes one of the later yum clean operations to fail. I fixed it, but I cannot upload the change as the server has no internet access.
I am new to CentOS6 as well as Redhawksdr, and I am trying to run the tar xzvfredhawk-yum-1.8.4-el6-i686.tar.gz instruction on page 24, section 2.3 and my terminal freezes. Anyone know what is wrong and how to fix it?
Try checking to see if yum is being locked by something else (though an error should be produced if this were the case):
ps aux | grep yum
If something else is locking yum, try killing it.
Also, take a look at your repositories in /etc/yum.repos.d. Are there any IP addresses in there that might cause a timeout? Try pinging any IPs that are in there: if you can't ping, remove them from /etc/yum.repos.d (do this by saving the file off somewhere else).
If neither of those work, please post the exact syntax you are using. If yum is waiting on an input, it will freeze (e.g., if the answer to David Duncan's question is "no", that would be your problem).
user2062950: I am assuming user2643765 is referring to section 2.3 of the REDHAWK user manual.
Please try this:
go to the location where the tar file is present, then run the following command:
tar xzvf redhawk-yum-1.8.4-el6-i686.tar.gz -C target_location