Skip to content
This repository has been archived by the owner on May 4, 2021. It is now read-only.

ADD Dockerfile command does not unpack tarballs #298

Open
andrewshadura opened this issue Jan 14, 2020 · 2 comments · Fixed by #309
Open

ADD Dockerfile command does not unpack tarballs #298

andrewshadura opened this issue Jan 14, 2020 · 2 comments · Fixed by #309
Labels
bug Something isn't working

Comments

@andrewshadura
Copy link

Describe the bug
ADD tarball.tar.gz / is supposed to unpack the said tarball into the root. Instead, it just copies it into it.

To Reproduce
The specific Dockerfile I ran into this at:

FROM scratch
    
ENV LANG=C.UTF-8
ENV LC_ALL=C.UTF-8

ARG DEBIAN_FRONTEND=noninteractive
  
ARG OSPACK=debian.tar.gz
ADD ${OSPACK} /

RUN apt-get update

Here, debian.tar.gz is a minimal Debian rootfs tarball.

Expected behavior
The tarball is unpacked, so that I can run commands using its contents.

Instead, I’m getting:

info	* Step 6/7 (modifyfs) : ADD debian.tar.gz /  (465a0d0c)
info	* Execute ADD debian.tar.gz /  (465a0d0c) took 91.261753ms
info	* Not committing step ADD debian.tar.gz /  (465a0d0c)
info	* Step 6/7 (modifyfs) : RUN apt-get update  (d6692f4c)
error	failed to execute build plan: execute stage: build stage 0: build node: do execute: execute step: cmd start: exec: "sh": executable file not found in $PATH
@yiranwang52 yiranwang52 added the bug Something isn't working label Jan 14, 2020
@andrewshadura
Copy link
Author

andrewshadura commented Mar 11, 2020 via email

@yiranwang52 yiranwang52 reopened this Mar 12, 2020
@yiranwang52
Copy link
Contributor

Let me keep the issue open until they are all supported

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants