Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Build clearlinux rootfs using clearlinux #48

Closed
jodh-intel opened this issue Jan 25, 2018 · 16 comments
Closed

Build clearlinux rootfs using clearlinux #48

jodh-intel opened this issue Jan 25, 2018 · 16 comments
Assignees
Labels
needs-help Request for extra help (technical, resource, etc)

Comments

@jodh-intel
Copy link
Contributor

Currently, rootfs-builder/clearlinux/Dockerfile.in builds the clearlinux rootfs using fedora 27. We should use clearlinux to build clearlinux.

See: #40 (comment)

@sohamdigheoss
Copy link

sohamdigheoss commented Feb 5, 2019

@jodh-intel Can I do this? If yes what tag to use will be used in place of @OS_VERSION@? latest or base?

@jodh-intel
Copy link
Contributor Author

Hi @sohamdigheoss - sure, it's all yours! ;) Github won't let me actually assign this issue to you, but this comment is enough for the team to see you're working on this.

I'd use the latest version of clearlinux.

@sohamdigheoss
Copy link

sohamdigheoss commented Feb 10, 2019

@jodh-intel I have encountered an issue while finding a bundle for gcc in clearlinux.
All of the bundles with gcc(c-basic,rust-basic,etc) have size greater than 1gb which seems a quite excessive to me.
Then I tried to create my own bundle but it required the mixer bundle which is 3gb in size.
I believe that gcc is required for installing GO so one of the possible solutions is to install and rremoving the bundle after installation is finished but i am not sure if there is further use for gcc and if removing it after use is a viable solution or not.
what do you think should be done here?

@jodh-intel
Copy link
Contributor Author

Thanks for investigating this @sohamdigheoss.

Any thoughts on this @bryteise?

@jodh-intel
Copy link
Contributor Author

Any update on this @sohamdigheoss?

Anyone else able to help out and test this with Clear Linux directly? F27 went EOL in November 2018 so we atleast need to update the clearlinux/Dockerfile to specify fedora:29 (or maybe just fedora?) But clearly, the ideal is to not require Fedora for Clear Linux at all ;)

/cc @bryteise.

@bryteise
Copy link

@jodh-intel I am just now seeing this sorry X(.

@sohamdigheoss I'm not sure on the requirement to have gcc or go in for the rootfs. If it is for building osbuilder then the go-basic bundle I would expect to be sufficient. Could you point me at the set of steps you are trying to run from fedora so I can get you the best set of bundles to duplicate this on Clear Linux?

@egernst
Copy link
Member

egernst commented Jul 17, 2019

while its a cool idea, I am not sure there's value-add, unless someone wants to help here.

@egernst egernst added the needs-help Request for extra help (technical, resource, etc) label Jul 17, 2019
@egernst
Copy link
Member

egernst commented Jul 17, 2019

WDYT @jodh-intel @bryteise @jcvenegas ?

@jodh-intel
Copy link
Contributor Author

The clearlinux dockerfile has now been updated to Fedora 30 so this could be closed. It's a bit of a shame though as CL is the only rootfs image not built using itself ;(

@bryteise
Copy link

I will take a shot at the rootfs creation.

@bryteise
Copy link

@egernst Mind assigning this to me?

@jodh-intel
Copy link
Contributor Author

@bryteise - thanks - all yours! ;)

@bryteise
Copy link

Hrm so looking at what this actually does, I'm a bit worried about the build time impact of switching to Clear Linux as it isn't trying to provide a streamlined rpm installation experience. Are there concerns about build time for these?

@devimc
Copy link

devimc commented Jul 23, 2019

@bryteise I don't think so, our biggest concern is to include packages/binaries that potentially can increase the attack surface and bring vulnerabilities.

@jcvenegas
Copy link
Member

@bryteise If bundle definition is not small enough today you can use an image base that uses at least rpm, in and keep the same way that the rootfs population works today ( via rpms). At least in that way the the config can look a bit more consistent. We did it in the past because the only bundle with rpm was os-clr-on-clr, a really big bundle for the our needs I am not sure if pundles now fix those issues.

@bryteise
Copy link

@jcvenegas We currently don't have a very size optimized rpm bundle largely due to the ecosystem using python and so it sits in the hundreds of megs. Still much smaller than the os-clr-on-clr bundle though.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs-help Request for extra help (technical, resource, etc)
Projects
None yet
Development

No branches or pull requests

6 participants