Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

k.Transform failed archive/tar: write too long #1093

Closed
wuestkamp opened this issue Jan 12, 2019 · 4 comments
Closed

k.Transform failed archive/tar: write too long #1093

wuestkamp opened this issue Jan 12, 2019 · 4 comments

Comments

@wuestkamp
Copy link

wuestkamp commented Jan 12, 2019

When running kompose up -vvv I'm getting:

INFO Building image 'eu.gcr.io/project/php:latest' from directory 'project_dir' 
DEBU Created temporary file /var/folders/yt/9pghpn1s5sq0bvnw0hmwljfr0000gn/T/kompose-image-build-069005223 for Docker image tarballing 
FATA Error while deploying application: k.Transform failed: Unable to build Docker image for service php: Unable to create a tarball: archive/tar: write too long 

I can push manually though without issues using docker push eu.gcr.io/project/php:latest

Why is this a problem here?
What is tarball used for?
Can I disable tarballing?

I saw #656 but is closed so wanted to open a new one. I'm having a Symfony project and removed already the vendor folder, no change.

Thanks,
Kim

@wuestkamp
Copy link
Author

So this only happens if I do this in my docker-compose.yml:

    php:
        build:
          context: .
          dockerfile: ./php-fpm/Dockerfile

if I leave it like this no error:

    php:
        build: ./php-fpm

But I need to use the context setting because I want to copy files in my Dockerfile:

ADD php-fpm/symfony.ini /etc/php7/conf.d/
ADD php-fpm/symfony.ini /etc/php7/cli/conf.d/
ADD php-fpm/xdebug.ini  /etc/php7/conf.d/

ADD php-fpm/symfony.pool.conf /etc/php7/php-fpm.d/

CMD ["php-fpm7", "-F"]

WORKDIR /var/www/symfony
COPY symfony .

Anyone got an idea?

@wuestkamp
Copy link
Author

Ok, this was because there were still deeply hidden symlinks in the context folder. So symlinks was the issue :)

@hangyan
Copy link
Contributor

hangyan commented Jan 1, 2020

related to #969

@rashad
Copy link

rashad commented Apr 20, 2020

Sorry for dumb question but I don't get what the issue is with symlinks and what should one do in case he has some (I do) ?

Thanks for your help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants