|
Bugzilla – Full Text Bug Listing |
| Summary: | official openSUSE docker image (opensuse/ namespace) is missing gzip | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Petr Vorel <petr.vorel> |
| Component: | Containers | Assignee: | Containers Team <containers-bugowner> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | asarai, fvogt, petr.vorel, rbrown, rbrown, rjschwei |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| See Also: | http://bugzilla.suse.com/show_bug.cgi?id=1127849 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Petr Vorel
2019-03-01 11:31:17 UTC
(In reply to Petr Vorel from comment #0) > Our official openSUSE images (both Leap and Tumbleweed) miss gzip image. Which images to you really mean? > https://github.com/docker-library/official-images/issues/5371 As you can see the "official-library" images of docker hub are not our official images. > 2) unofficial images https://hub.docker.com/r/opensuse/ has them. Why do you think they are unofficial, if we call them "official"? Sorry, I mixed the URL (but the github issue in https://github.com/docker-library/official-images/issues/5371 is correct). So once more again: our official images opensuse/leap and opensuse/tumbleweed from https://hub.docker.com/u/opensuse don't install gzip by default. Re-assigning to the containers module We are currently in the process of removing the "official" images[1], since the images that we actually have publishing control over are the ones in the opensuse/ namespace. Please use those, they are actually up-to-date and we have the ability to push updates to them immediately (while the "official" images don't have that luxury). We've tried to work around this issue before with the upstream maintainers (by making the "official" images point to ours) but that hasn't been resolved. Basically, this is a WONTFIX since we're going to be removing the images anyway and we have recommended against using them for at least a year now (though unfortunately that hasn't been well-publicised). [1]: https://github.com/docker-library/official-images/issues/5371 Well, the bug report is about opensuse/ images (the official ones) lack gzip. I'm trying to explain that all the time, I guess it should be fixed :). Maybe the "docker" in the title is misleading, I really mean *our* official images. [1] has been done, opensuse: images are now deprecated and thus unusable in docker (good). Users will search and start using opensuse/ (still good), but lacking basic packages can put them away to another distro. See also [2]. [1]: https://github.com/docker-library/official-images/issues/5371 [2] https://github.com/linux-test-project/ltp/commit/e478b949dd993072e50ddb907aab444c564ed34e (In reply to Petr Vorel from comment #5) > Well, the bug report is about opensuse/ images (the official ones) lack > gzip. I'm trying to explain that all the time, I guess it should be fixed > :). Maybe the "docker" in the title is misleading, I really mean *our* > official images. *Oh* sorry, my bad. Fabian would be the right person to ask about this (adding him to Cc). The base container is an environment for running zypper in a shell, so I don't see any reason to include any tools in the image that are not absolutely necessary. "basic package" is a way too broad attribute and would apply to tons of packages. It's worth of mentioning that all other distros we test in LTP have it (various versions of Debian, Ubuntu, Centos, Fedora and even the old opensuse: from Docker [1]). Many people wanting just usable distro will move away to other distros (see discussion in research "[Research] where is ping ?" where lots of people are against minimal but unusable images [1] https://github.com/linux-test-project/ltp/blob/master/.travis.yml [2] https://mailman.suse.de/mlarch/SuSE/research/2018/research.2018.12/msg00156.html (In reply to Petr Vorel from comment #8) > It's worth of mentioning that all other distros we test in LTP have it > (various versions of Debian, Ubuntu, Centos, Fedora and even the old > opensuse: from Docker [1]). Many people wanting just usable distro will move > away to other distros (see discussion in research "[Research] where is ping > ?" where lots of people are against minimal but unusable images > > [1] https://github.com/linux-test-project/ltp/blob/master/.travis.yml > [2] > https://mailman.suse.de/mlarch/SuSE/research/2018/research.2018.12/msg00156. > html Sure, but that's not what a base container is for. A base container is for installing packages to fit your use case, not for using it directly. (In reply to Petr Vorel from comment #8) > It's worth of mentioning that all other distros we test in LTP have it > (various versions of Debian, Ubuntu, Centos, Fedora and even the old > opensuse: from Docker [1]). Many people wanting just usable distro will move > away to other distros (see discussion in research "[Research] where is ping > ?" where lots of people are against minimal but unusable images > > [1] https://github.com/linux-test-project/ltp/blob/master/.travis.yml > [2] > https://mailman.suse.de/mlarch/SuSE/research/2018/research.2018.12/msg00156. > html Debian and Ubuntu only have gzip in their packages as a result of it being a hard requirement of dpkg I'd assume it's a similar story in Fedora and CentOS but I cant for the life of me figure out how to get such data out of dnf. Zypper has no such requirement, and therefore the absence of gzip is a considerable benefit of the openSUSE base container, which avoids this unnecessary bloat. Remember, OCI containers are intended to be used in a microservices architecture where dozens if not hundreds of these containers will be used. If gzip is not necessary in almost every-single usecase of the base container, then it most certainly should not be there. No user of a base container should ever assume anything besides the package-manager is present, and should be installing what they need as part of their container bootstrapping. Thank you both for info and sorry for wrong report. |