Since there doesn't appear to be a Kiwi forum but Kiwi is closely related to OBS, am asking this question here...
Issue:
Creating a docker image currentlly succeeds, but the image is ridiculously large considering the files in the image
I cannot find anything amiss in the build log (which is successful, but since I strongly feel the issue is created very near the end, I have posted the final 100 lines of the build log at http://susepaste.org/31489577
The phenomenom is repeatable and consistent.
Replicating the issue:
Install the correct version of Kiwi that supports docker
Install kiwi and kiwi-docs(During my investigation I've installed many more kiwi packages, but these are the minimal essentials)
Follow the instructions in "/usr/share/doc/packages/kiwi/examples/suse-13.1/suse-docker-container.readme" as follows
Then inspect the size of the target directory (In the above example /tmp/mycontainer)
Note that above I am recommending the exact code from documentation, whereas my log records describe my target directory as "mydocker-build-a"
As you might guess, I have run various docker builds from the same build directory but pointing to different target directories to test output without destroying previous attempts.
Monitoring, attempting to determine cause
My current speculation is based on repeatedly monitoring the size of the target (destination) directory during the Prep and Image creation step(the above kiwi command). The directory size appears to be very reasonable in size through most of the process (<120MB) until shortly before completion when it jumps to almost 600MB.
Speculation
I suspect that the original target file system is too small, and is enlarged later by some default and perhaps arbitrary number. I seem to remember something like this using dd(would be completely unrelated, but who knows if a similar occurence) where if a file is too small, then it is automatically expanded by a set amount, and I am speculating that when 100MB is too small, then another 500MB is concatenated automatically.
The exact suspect command (in the logs)
The full command follows which I believe creates the initial target. I don't know anything about this syntax which apparently is unique to kiwi(at least Google only lists instances where it shows up in kiwi)
Looking for ways to resolve, troubleshoot or either disabuse me of my speculation :) ...
TIA,
TSU
Issue:
Creating a docker image currentlly succeeds, but the image is ridiculously large considering the files in the image
I cannot find anything amiss in the build log (which is successful, but since I strongly feel the issue is created very near the end, I have posted the final 100 lines of the build log at http://susepaste.org/31489577
The phenomenom is repeatable and consistent.
Replicating the issue:
Install the correct version of Kiwi that supports docker
Code:
zypper ar http://ftp5.gwdg.de/pub/opensuse/repositories/Virtualization:/Appliances/openSUSE_13.1/Code:
zypper in kiwi kiwi-docsCode:
kiwi -p /usr/share/doc/packages/kiwi/examples/suse-13.1/suse-docker-container \
--root /tmp/mycontainerNote that above I am recommending the exact code from documentation, whereas my log records describe my target directory as "mydocker-build-a"
As you might guess, I have run various docker builds from the same build directory but pointing to different target directories to test output without destroying previous attempts.
Monitoring, attempting to determine cause
My current speculation is based on repeatedly monitoring the size of the target (destination) directory during the Prep and Image creation step(the above kiwi command). The directory size appears to be very reasonable in size through most of the process (<120MB) until shortly before completion when it jumps to almost 600MB.
Speculation
I suspect that the original target file system is too small, and is enlarged later by some default and perhaps arbitrary number. I seem to remember something like this using dd(would be completely unrelated, but who knows if a similar occurence) where if a file is too small, then it is automatically expanded by a set amount, and I am speculating that when 100MB is too small, then another 500MB is concatenated automatically.
The exact suspect command (in the logs)
The full command follows which I believe creates the initial target. I don't know anything about this syntax which apparently is unique to kiwi(at least Google only lists instances where it shows up in kiwi)
Code:
EXEC [touch /tmp/mydocker-build-a/.broken 2>&1]TIA,
TSU