#6145 docker fedora:21 has no man pages
Closed: Invalid None Opened 8 years ago by dachary.

Steps to reproduce
{{{
$ docker run -t -i fedora:21 bash

yum provides /usr/share/man/man1/ls.1.gz

fedora/21/x86_64/filelists_db | 25 MB 00:00:01
updates/21/x86_64/filelists_db | 13 MB 00:00:00
coreutils-8.22-19.fc21.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo : fedora
Matched from:
Filename : /usr/share/man/man1/ls.1.gz
coreutils-8.22-19.fc21.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo : @anaconda
Matched from:
Filename : /usr/share/man/man1/ls.1.gz

yum install coreutils

Package coreutils-8.22-19.fc21.x86_64 already installed and latest version
Nothing to do

ls -l /usr/share/man/man1/ls.1.gz

ls: cannot access /usr/share/man/man1/ls.1.gz: No such file or directory

yum install man

man ls

No manual entry for ls
}}}

see also https://github.com/fedora-cloud/docker-brew-fedora/issues/9#issuecomment-91881534


This is as intended by the cloud SIG and as such isn't a bug. It's specified in the .ks as part of "%packages --excludedocs --instLangs=en --nocore" as a result this isn't a rel-eng issue but rather one to take up with the Cloud SIG on their mailing list

I created https://fedorahosted.org/rel-eng/ticket/6146 as an enhancement request. It would be nice to add to this ticket a workaround to force the installation of manual pages. I don't know what a .ks is nor what %packages means in this context and I suspect I'm not the only one ;-)

Replying to [comment:3 dachary]:

I created https://fedorahosted.org/rel-eng/ticket/6146 as an enhancement request.

The enhancement request and discussion needs to go to the cloud list not here.

It would be nice to add to this ticket a workaround to force the installation of manual pages. I don't know what a .ks is nor what %packages means in this context and I suspect I'm not the only one ;-)

.ks is kickstart file, it's how the image in defined to be built. The %package section explicitly specifies the removal of all documentation from the image. So what is means is the lack of documentation is intended. If you wish to change this you need to discuss it with the Cloud SIG as they are the ones that make the decision as to what's included or not included in the images. It's nothing to do with release-engineering and hence this is not the place to discuss it.

Login to comment on this ticket.

Metadata