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

Install footprint has increased considerably in lxc-4.0.4 #3523

Open
sparlane opened this issue Aug 17, 2020 · 4 comments
Open

Install footprint has increased considerably in lxc-4.0.4 #3523

sparlane opened this issue Aug 17, 2020 · 4 comments
Labels
Feature New feature, not a bug

Comments

@sparlane
Copy link
Contributor

When we upgrade from lxc-4.0.1 to lxc-4.0.4 our initrd grew by 6.8MB (this represents >10% of the original size)

We build from source with the following configuration:
'--sysconfdir=/etc',
'--disable-doc',
'--disable-api-docs',
'--disable-apparmor',
'--disable-selinux',
'--enable-seccomp',
'--disable-examples',
'--disable-bash',
'--with-init-script=',
'--with-global-conf=/etc/lxc/lxc.conf',
'--with-distro=unknown',
GCC is 4.7.4 and 4.9.3, the initrd has the binaries stripped and then gziped

before strip is run, the lxc-* binaries are all 3.4M in 4.0.4 (in 4.0.3 they are 109->831K, most were ~120K)
after strip is run, most are now 951K (in 4.0.3 mostly 68K)

@brauner, I think this is a side effect of #3492

@stgraber
Copy link
Member

Yeah, I'd expect this to be a side effect of removing a whole bunch of internal symbols from our shared library.
I still think it's the right move overall, we shouldn't have our public library include a whole bunch of internal functions with tools using those symbols and so breaking should the library alone be upgraded/downgrade.

One option to get the best of both worlds would be to have an internal shared library which the tools use and which isn't versioned and must always be from the same build as the tools. This would let the individual binaries go back to being tiny while also not having our public library be used for this.

@sparlane
Copy link
Contributor Author

How can I help to resolve this so we can have both?

Also what is the timing of lxc-4.0.5 likely to be?

Thanks

@stgraber
Copy link
Member

No clear timing at this point. We release when we feel we have enough important fixes accumulated.

As for adding an internal shared library, that would be a question for @brauner

@brauner
Copy link
Member

brauner commented Aug 30, 2020

How can I help to resolve this so we can have both?

Also what is the timing of lxc-4.0.5 likely to be?

Thanks

Hm, I'm happy to merge something that would fix this. Do you feel up for this task @sparlane?

@brauner brauner added the Feature New feature, not a bug label Aug 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature, not a bug
Development

No branches or pull requests

3 participants