text: When I do a ice login -k I get the following response
  Target is container cloud. Invoking cloud service... Authentication with container cloud service completed successfully 2014/12/10 22:22:12 Error response from daemon: (Code: 404; Headers: map[X-Backside-Transport:[FAIL FAIL] Server:[gunicorn/18.0] X-Global-Transaction-Id:[2475987921] Set-Cookie:[DPJSESSIONID=XXXX; Path=/; Domain=.registry-ice.ng.bluemix.net] Connection:[Keep-Alive] Date:[Wed, 10 Dec 2014 21:19:40 GMT] Content-Type:[text/html] X-Docker-Registry-Version:[0.8.1] X-Docker-Registry-Config:[swift] X-Client-Ip:X]])
  Succesfully but error?
  Then when I do a ice push --local I get requested to authenticate with username/password/email but I can't seem to get it right, same credentials are needed to login to the bluemix website dashboard I presume?
  did you find a work around? I am stuck at the same place as you are. I am able to authenticate by cf login. Then I try using the ice utility with the api key and I get the same error.
  Answer by Alaa Youssef (196) | Dec 11, 2014 at 11:44 AM
  Hi Drams,
  I went through the different responses and things you've done and you are certainly getting there. Let me try to clarify what is needed to successfully access the IBM Containers service, and separate that out from any other Bluemix id or org or .... As you know Bluemix is a big umbrella for many many services, each with its unique angle.
  Once you have selected the IBM Containers service from the IBM Bluemix catalog, and it is provisioned for you, you get a UI dashboard that includes two pieces of info which are all what you need to continue experimenting with this service from that moment onwards. These two pieces are:
  1- API Key (think of it as your personal id to access the service)
  2- Registry host, and your namespace (you actually selected your namespace during the service provisioning dialog) The experimental registry host we have at the moment is
  registry-ice.ng.bluemix.net so that should be what you see in the dashboard and what you use.
  Now, you can login using:
  ice login -k API_KEY -R registry-ice.ng.bluemix.net
  (You should not really need to specify the -R option each time you login. I am being extra cautious here in case you set the wrong registry in ice one way or the other during your previous experimental attempts)
  The names of all the images that you push should be prefixed with:
  registry-ice.ng.bluemix.net/<your namespace>
  I saw some good examples from Sam, in the previous responses, on image naming. Here is one more. My namespace is
  youssef. To push an image named
  mynodejs, that I already built using docker on my localhost I do:
  ice --local tag mynodejs registry-ice.ng.bluemix.net/youssef/mynodejs ice --local push registry-ice.ng.bluemix.net/youssef/mynodejs
  Now to check that it was successfully pushed, I can do:
  ice images
  To use it to create and start a container, I need to use the run command:
  ice run --name mycontainer registry-ice.ng.bluemix.net/youssef/mynodejs
  To verify that the container is running, I do:
  ice ps
  Then I use the ice ip commands to request an ip address, and bind it to mycontainer. The commands I find useful here are:
  ice ip request ice ip bind ice ip list --all
  To get help on any of these or other commands, you can do for example:
  ice ip bind --help
  Please let me know if this was helpful? I am also curious to know what kind of application you are to build using IBM Containers.
  Thank you Youssef, and everyone else. I was slowly getting there indeed. It's the first time I've got this much (fast) support while using any IBM related product. Thanks a million.
  I started from scratch today, with a new work space and so on. I thought I still needed approval since most of the time I still get the message in Google Chrome (bug?) "It looks like the administrator in your organization has already requested the service. We will notify him/her when the service is ready for you to use."
  I was able to push my image and actually run it, what I am missing though is an option to expose (something like -P or -p 8080:8080) I don't see it under parameters for the run option. The IP is assigned but I can't see any priv/pub ports in ice ps.
  I just trying the service out, I made a little Linkshortening application which I'm trying to up and running using Docker now. Mainly test purposes for now. :)
  Hi, thanks for the feedback! We don't currently expose the -p portion for the current time being. The only ports that we expose in containers are : 22,80,443,9080,9443 for public internet access. We are looking at improving this.
  It would be very helpful to state the ports exposed in the Container service documentation. This sentence from the docs:
  To simulate the conditions of IBM Containers, use the -P option when you are testing locally because this option maps all ports of your running container, which matches the IBM Containers run time.
  makes it sound like all ports exposed.
  Answer by LinSun (461) | Dec 10, 2014 at 04:06 PM
  Hi there,
  When you use ice login -k $API_key, you want to pass in the API_key, not your bluemix website dashboard password. Note you can always go to your deployed IBM container service instance to retrieve the API_Key, assuming you have already deployed the IBM container service instance.
  Can you try if you can do "docker login -u user -p $API_key -e a@b.c registry-ice.ng.bluemix.net"?
  Thanks.
  docker login -u USERNAME -p APIKEY -e EMAIL registry-ice.ng.bluemix.net works: Login Succeeded
  ice login -k APIKEY: Authentication with container cloud service completed successfully 2014/12/10 23:42:14 Error response from daemon: (Code: 404;
  Yet when I'm trying to do is push my Docker image, but I can't seem to get it working. It requests me to fill in username, password and email address and then fails.: drissamri Password: Email: EMAIL 2014/12/11 00:08:17 Error response from daemon: Wrong login/password, please try again
  Thanks for the additional info! As Gosia spotted, please use the correct url: registry-ice.ng.bluemix.net/driss/linkshortener for your image, assuming driss is the registry namespace you specified at your container service instance panel. Let us know if this helps!!
  Answer by JakeKitchener (361) | Dec 10, 2014 at 06:52 PM
  @drams. This is a bit odd, but when you do the push use your ibmid for the email. Then use your API key for the password. It's a little odd but it should work. I've run into this issue as well. In theory once you do the ice login it should not make you auth again. We will investigate further.
  Answer by Gosia Steinder (136) | Dec 10, 2014 at 07:03 PM
  Please check your image tag. It should include full registry path, i.e. it should look as registry-ice.ng.bluemix.net//. Try registry-ice.ng.bluemix.net/driss/linkshortener.
  Answer by Alaa Youssef (196) | Dec 11, 2014 at 12:44 AM
  You can do
  ice info to see what the registry host is set to? should be
  registry-ice.ng.bluemix.net
  You can also add
  -R registry-ice.ng.bluemix.net to your ice login command:
  ice login -k API_KEY -R registry-ice.ng.bluemix.net
  That should work.
  ice login -k APIKEY -R registry-ice.ng.bluemix.net Target is container cloud. Invoking cloud service... Authentication with container cloud service completed successfully Login Succeeded
  So far so good, it did seem like my username was attached to registry host.
  But again, when I try to do a push
  bash-3.2$: ...
  Which username is this refering to since my IBM username is my email. I've tried my oraganization name. And for password I've try my IBM password and also the API key.
  You are tagging your image with registry-ice.bluemix.net instead of registry-ice.ng.bluemix.net. Please try this
  Retag image
  ice --local tag registry-ice.bluemix.net/driss/linkshortener registry-ice.ng.bluemix.net/driss/linkshortener
  Then repush.
  ice --local push registry-ice.ng.bluemix.net/driss/linkshortener
  Done. Same result, yet now I am able to login when I give the credentials, which should not be necessary?
  Target is local host. Invoking docker with the given arguments... bash-3.2$ ice --local push registry-ice.ng.bluemix.net/driss/linkshortener Target is local host. Invoking docker with the given arguments... The push refers to a repository [registry-ice.ng.bluemix.net/driss/linkshortener] (len: 1) Sending image list Please login prior to push: Username (user): Login Succeede The push refers to a repository [registry-ice.ng.bluemix.net/driss/linkshortener] (len: 1) Sending image list 2014/12/11 11:52:34 Error: Status 401 trying to push repository driss/linkshortener: {"error": "Account linkshortener not authorized for namespace driss"}
  Linkshortener is the name I want to give to my service, I'm not sure how everything relates to each other yet. Problem of trying to be an early adopter I guess. :-) I deleted my space and service yesterday, do I need to be approved again now?
  39 people are following this question.