Skip to content
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.

rkt downloads and extracts every docker image layer #3831

Closed
daledude opened this issue Oct 18, 2017 · 4 comments
Closed

rkt downloads and extracts every docker image layer #3831

daledude opened this issue Oct 18, 2017 · 4 comments

Comments

@daledude
Copy link

daledude commented Oct 18, 2017

Environment

rkt Version: 1.29.0
appc Version: 0.8.11
Go Version: go1.8.3
Go OS/Arch: linux/amd64
Features: -TPM +SDJOURNAL
--
Linux 4.11.0-14-generic x86_64
--
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
--
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

What did you do?
rkt run or rkt fetch docker:// image that has multiple layers after a update to a smaller layer.

What did you expect to see?
rkt download only changed layer and extract that.

What did you see instead?
rkt downloads ALL layers and re-extracts all of them to build aci.

I have base images that are 1 gig in size and having these layers downloaded and extracted every time a smaller upper layer is changed can take a very long time. Make dev testing with rkt frustrating. Maybe I'm missing something.

@daledude
Copy link
Author

daledude commented Dec 8, 2017

Project dead so moving on.

@daledude daledude closed this as completed Dec 8, 2017
@mprasil
Copy link

mprasil commented Dec 9, 2017

Can we reopen this? It's still a bug/issue in rkt for rest of us.

@alban alban reopened this Dec 12, 2017
@mprasil
Copy link

mprasil commented Dec 21, 2017

@daledude why is this closed again?

@iaguis iaguis reopened this Jan 9, 2018
@iaguis
Copy link
Member

iaguis commented Jan 9, 2018

Please don't close this issue again as we'd like to keep track of it

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

No branches or pull requests

4 participants