<p>I am attempting to run a docker-compose file using <code>kompose up</code>. I am on Mac OS High Sierra, running latest and greatest versions of everything (Docker CE 17.12.0, VirtualBox 5.2.8 and kompose 1.11.0). </p>

<p>My docker-compose file is:</p>

<pre><code>version: '2'

services:
  es:
    build: ./elastic-search
    image: horcle/es
    ports:
     - "9200:9200"
     - "9300:9300"  
    volumes:
     - ./data:/elasticsearch/data
  tab:
    build: ./nlp-tab
    image: horcle/nlptab
    ports:
     - "8000:8000"
    volumes:
     - ./data:/app/data
</code></pre>

<p>When I run <code>kompose up</code> the first image gets successfully built and pushed to Docker.io. However, I get the following error on the second image: <code>FATA Error while deploying application: k.Transform failed: Unable to build Docker image for service tab: Unable to create a tarball: archive/tar: write too long</code></p>

<p>I Googled this, and the issue appears to be with symlinks, which are nowhere in the directory I am using to build this image.</p>

<p>As a test, I did a <code>docker build -t horcle/nlptab .</code> followed by a successful push to Docker.io using <code>docker push horcle/nlptab</code>. Also, <code>docker-compose up</code> runs just fine, as well.</p>

<p>I'm not exactly sure why I cannot run a <code>kompose up</code> to do the same thing.</p>

<p>Did you find a solution for this already? if not, try running below command and find out if any symlinks exist.
<code>ls -laR . | grep -B 5 " -&gt; "</code></p>

<p>This may help you find dependencies from node_modules like folders that may be using symlinks.</p>
