We are trying to do a container based setup of APIM 4.0.0 on Openshift and for that trying to pull the image of the latest version of WSO2 APIM from docker using a valid subscription but not able to pull and getting the below error. Can someone please suggest how this issue can be fixed?
[admcoe#blrocpimpbastion ~]$ sudo docker pull docker.wso2.com/wso2am-kubernetes:latest
Trying to pull repository docker.wso2.com/wso2am-kubernetes ...
Pulling repository docker.wso2.com/wso2am-kubernetes
invalid character '<' looking for beginning of value
[admcoe#blrocpimpbastion ~]$ sudo docker pull docker.wso2.com/wso2am-kubernetes
Using default tag: latest
Trying to pull repository docker.wso2.com/wso2am-kubernetes ...
Pulling repository docker.wso2.com/wso2am-kubernetes
invalid character '<' looking for beginning of value
Thanks,
Suman
You can do the following.
Login to docker.wso2.com
docker login docker.wso2.com
Pull the latest docker image of APIM v4.
docker pull docker.wso2.com/wso2am:4.0.0.0
Related
Docker pull resulting the following error, we are trying to pull the image from artifactory (docker repo)
% docker pull artifactory.myorg.com/docker/axyu1325/kargo:0.3.0
Error response from daemon:
Missing or empty Content-Length header
Upgrade artifactory to 7.0.0 or later, or downgrade your docker client.
I would like to docker pull a specific version of Keycloak but I have get this error:
Error response from daemon: pull access denied for jboss/keycloak-3.4.3, repository does not exist or may require 'docker login'
when I try this command:
docker pull jboss/keycloak-3.4.3
How I can get a specific version of Keycloak with docker ?
Do I have to modify the dockerfile?
The proper version is 3.4.3.Final - see the tags.
I am a newbie to Docker and getting hands on with Docker Toolbox in my PC which is behind a corporate proxy. After some SO answers I was able to solve X509 Unauth cert and Proxy issues. Then I was able to do docker search elastic which lists all the images in the dockerhub. But when I tried to pull the official image with docker pull elastic it throws below error. Tried a couple of solutions from google to do docker login and checked but nothing is working out so far. Any solution would be much apprecicated.
raj#localpc MINGW64 ~/DockerWS/app1
$ docker search elastic
NAME DESCRIPTION
STARS OFFICIAL AUTOMATED
elasticsearch Elasticsearch is a powerful open source se
... 2667 [OK]
kibana Kibana gives shape to any kind of data s.
.. 1081 [OK]
itzg/elasticsearch Provides an easily configurable Elasticsea
... 63 [OK]
nshou/elasticsearch-kibana Elasticsearch-6.1.2 Kibana-6.1.2
48 [OK]
kubernetes/fluentd-elasticsearch An image that ingests Docker container log
... 21
raj#localpc MINGW64 ~/DockerWS/app1
$ docker pull elastic
Using default tag: latest
Error response from daemon: unauthorized: authentication required
Thanks.
Raj
The reason is that there is no elastic image available with exactly that name. The search results show for instance elasticsearch or nshou/elasticsearch-kibana which have to be used in the docker pull command.
docker pull elasticsearch would be the solution to use the official ElasticSearch image.
Instead of searching in the terminal you could also use DockerHub directy and copy&paste the docker pull command shown in the right section, e.g. https://hub.docker.com/_/elasticsearch/
The Dockerhub elastic search image has beed deprecated. You can try to pull from the official images using:
docker pull docker.elastic.co/elasticsearch/elasticsearch:6.1.2
I'm at my wits trying to get Docker images from Google Container Registry onto a Google Compute Engine instance. (The images I need have been successfully uploaded to GCR.)
I've logged in using gcloud auth login and then tried gcloud docker pull -- us.gcr.io/app-999/app which results in ERROR: (gcloud.docker) Docker is not installed..
I've tried to authenticate using oauth and pulling via a normal docker call. I see my credentials when I look at the file at .docker/config.json. Doing that, it looks like it's going to work, but ultimatly ends like this:
mbname#instance-1 ~ $ docker pull -- us.gcr.io/app-999/app
Using default tag: latest
latest: Pulling from app-999/app
b7f33cc0b48e: Pulling fs layer
43a564ae36a3: Pulling fs layer
b294f0e7874b: Pulling fs layer
eb34a236f836: Waiting
error pulling image configuration: unauthorized: authentication required
which looks like progress, because at least it attempted to download something.
I've tried both of these things on my local machine as well and both methods were successful.
Am I missing something?
Thanks for your help.
P.S. I've also tried loading a container from another registry (
Docker Hub) and that worked fine, but I need more than one container and want to keep expenses down.
After contacting Google support they informed me that there is a bug in the CoreOS gcloud alias. This bug is fixed by overwriting the alias in the shell as follows:
alias gcloud='(docker images google/cloud-sdk || docker pull google/cloud-sdk) > /dev/null;docker run -t -i --net=host -v $HOME/.config:/.config -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker google/cloud-sdk gcloud'
I've tried this and it works now.
docker should be included in the latest versions of gcloud. You can update to the latest version of gcloud by running gcloud components update
I've just come over from tutum and and am trying to deploy to a docker cloud repository. I've created the repository and have tagged an existing image:
docker tag deploy foo/rtb
When I attempt to push my tagged image up like so:
docker push foo/rtb
I get this:
The push refers to a repository [docker.io/foo/rtb] (len: 0)
18118bb6b8ef: Preparing
unauthorized: access to the requested resource is not authorized
The repository exists and I've logged in to docker. Is there something I'm missing?
Interestingly enough, if I try to delete the image I get an error like this:
Error response from daemon: conflict: unable to delete 18118bb6b8ef
(must be forced) - image is referenced in one or more repositories
Error: failed to remove images: [18118bb6b8ef]
I had been using docker 1.9.1. That's the version in the Fedora 23 repo.
The kind folks at docker tech support recommended I upgrade to the latest 1.10.3
Upgrading then doing
docker logout
followed by
docker login
fixed everything up.
Did you tag your image ?
docker build --tag docker.io/<yourdockerhubname>/<appname> .
docker build --tag docker.io/moskalr/rtb .
docker push docker.io/<yourdockerhubname>/<appname>
docker push docker.io/moskalr/rtb
the push should respond with something which mentions the dockerhub image name