-
Notifications
You must be signed in to change notification settings - Fork 174
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
bootstrap.iso for rhel 7.7 having some issues #8616
Comments
Please find the logs below: tether tmpfs size before copying libraries: ++ cp /sbin/rngd /mnt/containerfs/.tether/bin/rngd cat: write error: No space left on device ++ echo 'switching to the new mount' |
@aviratna It seems that the tmpfs Line 157 in 9becae4
I'll try to fix it. And a workaround is to increase the size like doubling it and build the bootstrop.iso again. And could you help do a test with this pr: #8618 |
Thank you @YanzhaoLi
will try the new bootstrap.iso and update here.. |
@YanzhaoLi We are getting below error after building with above changes mentioned. Error in file: [ 4.921772] Error: Driver 'pcspkr' is already registered, aborting... ++ mount -t tmpfs -o size=m tmpfs /mnt/containerfs/.tether/ /bin/repoinit: line 36: cannot create temp file for here-document: No space left on device Failed to get D-Bus connection: Operation not permitted Feb 17 2020 02:38:51.685Z ERROR Starting entropy failed with "fork/exec : no such file or directory" Feb 17 2020 02:38:51.686Z ERROR Failed to start extension Entropy: fork/exec : no such file or directory Feb 17 2020 02:38:51.696Z ERROR fork/exec : no such file or directory Please find the detailed tether.debug log below, not able to upload the file:
|
same as CentOS 7.7 including the kernel version. CentOS 7.7. is built from RHEL 7.7. SRPMs minus branding. BTW, the build containers that I am using are non-privileged. Should I be building from privileged containers? |
@malikkal I don't think it matters. |
@YanzhaoLi any updates on this, please? |
@malikkal Still in investigation and to find the solution might not be a trivial. |
@YanzhaoLi okay, thanks mate. In parallel, let me also revert to 7.5 or older and see if it helps reducing the size. |
rhel7.4 (bootstrap.iso is 273 MB) rhel7.5 (bootstrap.iso is 310 MB) |
Looking at this after call last week.
The tmpfs is supposed to be very nearly full - it's size it calculated based on the size of the files needed. Ideally we'd be able to hit 100% perfectly so as to use the minimum number of memory pages, but some tolerance is useful. As @YanzhaoLi noted, 354MB is way more than I'd expect for a bootstrap iso. This line looks wrong to me - there's zero reason for us to have I think it likely that a mistake was made when determining the library dependencies for The probable reason for the out of space issues is that there are a lot of new libraries introduced by updates for centos7.5 and those libraries are not matched by the list used to calculate the necessary tmpfs size: Line 19 in 1967d0c
This should not be fixed just by adding the new libraries to the list used to calculate the tmpfs size - it should be fixed by determining the actual runtime dependencies used by rngd and iptables for the operations the tether requires. Additionally there is a double copy of the iptables libraries into vic/isos/base/repos/centos-7/init.sh Line 82 in 6729b55
I assume this is because something has a hardcoded library path suffix but this would be better addressed with a symlink from /.tether/usr/lib64 to /.tether/lib64 as is the same set of libraries. Currently this will be doubling the footprint of any library binaries which definitely will not be accounted for in the tmpfs size calculation.
|
Reference: #8569 #8575
We tried with rhel 7.7 & vic 1.5.4 we are getting same issue.
Summary:
bootstrap.iso file builds successfully and containers could startup however, tether doesn't start (refer debug attached) and container fails with "docker: Error response from daemon: Server error from portlayer: unable to wait for process launch status: container VM has unexpectedly powered off."
vSphere and vCenter Server version
vSphere 6.7u2
VIC version
VIC Version: 1.5.4
@YanzhaoLi
@DanielXiao
@malikkal
@hickeng
The text was updated successfully, but these errors were encountered: