Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define image test suite - functionality that's expected to work in toolbox images #385

Open
Jmennius opened this issue Feb 29, 2020 · 5 comments
Labels
1. Feature request A request for a new feature 2. Documentation The issue is related to the user documentation

Comments

@Jmennius
Copy link
Collaborator

I am willing to work on Debian and Ubuntu images and I would like to have some kind of a checklist of functionality that is expected to work in toolbox images.
I do not use toolbox actively yet so it is hard for me to define, some things are relatively obvious like home directory, DNS resolver, GUI apps - what else?

@HarryMichal
Copy link
Member

Hi @Jmennius! There is a section in the README called Image Requirements.

@Jmennius
Copy link
Collaborator Author

Hey @HarryMichal!

The Image Requirements section looks more about the toolbox tool itself (its dependencies basically?).

What I want to clarify is a set of functionality that the user of a toolbox container can/should expect of it (so that we could align it between distributions).
For example, in Fedora images we have git, tree, flatpak-spawn, gnupg, tracerout, tcpdump, etc added - I want some minimal formal description of that so that I can prepare an equivalent for Debian/Ubuntu (so that it wouldn't be random or just what I like/use, you know).

@tigerpaws2
Copy link

The definition of the Dockerfile (which is I suspect what you really want) is in the images/fedora directory. You should be able to translate that to Debian and Ubuntu.

@HarryMichal HarryMichal added 2. Documentation The issue is related to the user documentation 1. Feature request A request for a new feature labels Sep 10, 2020
@HarryMichal
Copy link
Member

I see now what you're saying, @Jmennius. You can take a look at Toolbox's .spec file. There are two extra packages defined that hold the packages that we need/want in a toolbox image: toolbox-support and toolbox-experience. Funnily enough, even though those two exist, they are not used in the Dockerfiles used for creating fedora-toolbox images but they use their own textfiles that hold the same list of packages. I want to fix that in the near future.

@Jmennius
Copy link
Collaborator Author

I see now what you're saying, @Jmennius. You can take a look at Toolbox's .spec file. There are two extra packages defined that hold the packages that we need/want in a toolbox image: toolbox-support and toolbox-experience. Funnily enough, even though those two exist, they are not used in the Dockerfiles used for creating fedora-toolbox images but they use their own textfiles that hold the same list of packages. I want to fix that in the near future.

Sounds great!
I'll try to align #483.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. Feature request A request for a new feature 2. Documentation The issue is related to the user documentation
Projects
None yet
Development

No branches or pull requests

3 participants