fatal: Not a git repository while building site through Docker build

[coolbrg]

Hi,

I am getting following errors while building Docker build

➜  atomic-site git:(build_fix) ✗ ./docker.sh 
Sending build context to Docker daemon 27.43 MB
Step 1 : FROM fedora:23
 ---> 3944b65d6ed6
Step 2 : MAINTAINER [email protected]
 ---> Using cache
 ---> 6c8d31f469ea
Step 3 : WORKDIR /tmp
 ---> Using cache
 ---> bad340bbe395
Step 4 : RUN dnf install -y tar libcurl-devel zlib-devel patch rubygem-bundler ruby-devel git make gcc gcc-c++ redhat-rpm-config && dnf clean all
 ---> Using cache
 ---> 2e22b2e68693
Step 5 : ADD config.rb /tmp/config.rb
 ---> Using cache
 ---> 5bb930c2556c
Step 6 : ADD Gemfile /tmp/Gemfile
 ---> Using cache
 ---> cd8f7277ee0e
Step 7 : ADD Gemfile.lock /tmp/Gemfile.lock
 ---> Using cache
 ---> e87dbf26294e
Step 8 : ADD lib /tmp/lib
 ---> Using cache
 ---> 79401607dae4
Step 9 : RUN bundle install
 ---> Using cache
 ---> 26b5551e2e95
Step 10 : EXPOSE 4567
 ---> Using cache
 ---> f8152326bd01
Step 11 : ENTRYPOINT bundle exec
 ---> Using cache
 ---> f32491e251fa
Step 12 : CMD middleman server
 ---> Using cache
 ---> 9f6418bb1840
Successfully built 9f6418bb1840
== The Middleman is loading

Updating git submodules...
fatal: Not a git repository (or any of the parent directories): .git

fatal: Not a git repository (or any of the parent directories): .git

Other observations:

• Opening 127.0.0.1:4567 in browsing running the site
• No success message or info that site is running now etc etc

[jberkus]

1. The "not a git repository" is a bogus error generated by Middleman. I'll add a note to Build.
2. Yeah, I've tried inserting an echo to say "the site is now running", but once control gets handed off to Middleman the line is never reached. Ideas?

[coolbrg]

Yeah, I've tried inserting an echo to say "the site is now running", but once control gets handed off to Middleman the line is never reached. Ideas?

@jberkus No idea at the moment 😄 . Will try to look for it.

[jlebon]

I think a simple "Starting Middleman" right before docker run should suffice. Heck, that script should probably have set +x to begin with.

[jberkus]

I'll admit that I don't actually use docker.sh ... gonna look at the atomicapp first.