Bug 1094773 - timezone package missing from default install
timezone package missing from default install
Status: RESOLVED INVALID
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Containers
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: Fabian Vogt
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-27 11:34 UTC by William Brown
Modified: 2018-05-30 09:24 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description William Brown 2018-05-27 11:34:03 UTC
The timezone package is missing from opensuse/tumbleweed container images. This affects deployments that may rely on timezone information. As this is a reasonably important (and small) feature to have included, it would help aid deployment if it was included by default.
Comment 1 Thorsten Kukuk 2018-05-28 07:24:13 UTC
If your application depends on timezone information, it should pull them into the container. Putting everything into the base container makes them again big and fat for no use of most containers.
Comment 2 Fabian Vogt 2018-05-28 07:25:50 UTC
The base container has a single job: Provide a usable zypper.

How does it affect deployments? The base container itself shouldn't be deployed directly, so you need timezone to be installed you should adjust your derived image config.
Comment 3 William Brown 2018-05-30 09:08:44 UTC
Okay, from your comments I understand the issue now. It seems we have a difference in our understanding of what the base container image should be. You have accurately stated the container is "the minimum possible to allow zypper to operate". I understood the base container to be "the minimal system in which I can deploy an application into". Having had experience with other distro container bases which contain timezone data, this was my assumption.

So I would still propose that timezone be included. Of course, the "just one more thing" trap should be avoided, but timezone is universally helpful to deployments (and appears to be the standard for other distro containers).

If you feel that the role should only be to provide zypper support, then feel free to close this issue. But it may be good to "document" the intent of the container's configuration somewhere. Alternately, please consider that it's counter intuitive as a design in my view, and that the minimal container should contain a minimal supportive application platform IE zypper + key libraries.

Thank you for your time,
Comment 4 Fabian Vogt 2018-05-30 09:24:56 UTC
(In reply to William Brown from comment #3)
> Okay, from your comments I understand the issue now. It seems we have a
> difference in our understanding of what the base container image should be.
> You have accurately stated the container is "the minimum possible to allow
> zypper to operate". I understood the base container to be "the minimal
> system in which I can deploy an application into".

You can - you just need to deploy it correctly, which means installing dependencies.

> Having had experience
> with other distro container bases which contain timezone data, this was my
> assumption.

> So I would still propose that timezone be included. Of course, the "just one
> more thing" trap should be avoided, but timezone is universally helpful to
> deployments (and appears to be the standard for other distro containers).

They probably contain that for other reasons, maybe the package manager requires the timezone data.

> If you feel that the role should only be to provide zypper support, then
> feel free to close this issue. But it may be good to "document" the intent
> of the container's configuration somewhere.

I don't think this needs to be documented - the assumption that a certain package is already installed is invalid by itself. It can change at any time, we can't just add a list of packages which aren't installed.

> Alternately, please consider
> that it's counter intuitive as a design in my view, and that the minimal
> container should contain a minimal supportive application platform IE zypper
> + key libraries.

"key libraries" can't be defined. Some might even say that the container should be LSB compatible, which means pulling in X and some GUI toolkits.
Therefore the base container has only the single and well defined goal: Allow package installation.

> Thank you for your time,