Docker Community Forums

Share and learn in the Docker community.

Unable to create new service from GUI


(Andrelackmann) #1

When I try and create a new service, using https://cloud.docker.com/_/service/wizard/config?image=gekkie/newrelic-cloudwatch I get a javascript error in the console and the page is never able to be submitted. I’m using Chrome on a Mac (if that makes any difference). Error shown:

Unhandled rejection TypeError: Cannot convert undefined or null to object
    at t.value (https://cloud.docker.com/0.0.1cadf015b3a0ef8b3a40.js:23:13753)
    at https://cloud.docker.com/0.0.1cadf015b3a0ef8b3a40.js:23:13150
From previous event:
    at https://cloud.docker.com/0.0.1cadf015b3a0ef8b3a40.js:23:13069
From previous event:
    at t.value (https://cloud.docker.com/0.0.1cadf015b3a0ef8b3a40.js:23:12925)
    at r.notifyAll (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:9:29899)
    at r.close (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:49:30648)
    at r.closeAll (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:8:10207)
    at r.perform (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:8:9653)
    at o.perform (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:8:9570)
    at o.perform (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:3:31108)
    at Object.O [as flushBatchedUpdates] (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:3:31277)
    at r.closeAll (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:8:10207)
    at r.perform (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:8:9653)
    at Object.batchedUpdates (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:19:19772)
    at Object.u [as enqueueUpdate] (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:3:30322)
    at r (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:10:3183)
    at Object.enqueueSetState (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:10:4042)
    at n.r.setState (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:19:16656)
    at n.handleChange (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:47:25726)
    at l (https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:20:6720)
    at https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:69:504
    at https://cloud.docker.com/main.4b3a4d443cdd8a10fa17.js:65:12849

(Ziontech) #2

I’m getting this too :frowning: Does DockerCloud not have any form of automated testing going on to catch issues like this before they completely cripple the service?


(Mehdig) #3

This is related to a bug that was introduced with service editor for service images without exposed ports. Going forward that will be a use case to look for. Working on a fix that should be made available soon. Sorry for the inconvenience.


(Mehdig) #4

This issue should be resolved now.


(Andrelackmann) #5

Cool. Working for me.


(Ryan Kennedy) #6