Image build fails about docker-api HOT 8 CLOSED

Could you post the generated Dockerfile? It's odd that it's complaining about an ASCII character -- I've never seen that before.

The second error you're referring to occurs when the build process fails.

from docker-api.

@nahiluhmot

This is the dockerfile that gets generated.

FROM jordansissel/system:debian-6.0.8
          RUN apt-get update
          RUN apt-get install -y openssh-server openssh-client
        RUN mkdir -p /var/run/sshd
        RUN echo root:root | chpasswd
RUN apt-get install -yq lsb-release wget net-tools ruby rubygems ruby1.8-dev libaugeas-dev libaugeas-ruby ntpdate locales-all

RUN REALLY_GEM_UPDATE_SYSTEM=1 gem update --system --no-ri --no-rdoc
        EXPOSE 22
        CMD ["/sbin/init"]

for the second error, is there a way to report back in which step or why the build fails?

Cheers

from docker-api.

The invalid character 'u' after top-level value error seems to come from the json parser in go, hmm. Can you take a look in the docker logs?

from docker-api.

@wader

only getting this:

2014/04/30 16:45:24 POST /v1.10/build?rm=true
[/var/lib/docker|cdc56c92] +job build()
invalid character 'u' after top-level value
[/var/lib/docker|cdc56c92] -job build() = ERR (1)

from docker-api.

Did some digging. Tried to restart docker but failed to start with this:

[/var/lib/docker|dca0e664] +job serveapi(unix:///var/run/docker.sock)
[/var/lib/docker|dca0e664] +job initserver()
[/var/lib/docker|dca0e664.initserver()] Creating server
2014/04/30 17:19:47 Listening for HTTP on unix (/var/run/docker.sock)
Couldn't create Tag store: invalid character 'u' after top-level value
[/var/lib/docker|dca0e664] -job initserver() = ERR (1)
2014/04/30 17:19:48 Couldn't create Tag store: invalid character 'u' after top-level value

Looks like that an image was b0rked somewhere.
I've removed docker and all dirs and starting over and seems to work now.

Wonder if it all the errors i've seen are connected with this.

from docker-api.

I cleaned up the whole docker directory of the node that failed to start docker, and everything seems to be stable at the moment.
Seems some images in docker went corrupt or something.

Unless logging wise you want to fix something i think we can close this issue?

from docker-api.

Thanks for following up, @electrical!

from docker-api.

No problem @bfulton Docker is very cool and i think i abuse it in a few ways, hopefully we can all improve it along the way :-)

from docker-api.