You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ sysbox-runc --version
sysbox-runc
edition: Community Edition (CE)
version: 0.6.3
commit: e6ca9b930c43c0f20bb93ef3ef6af5bd49fd88ce
built at: Tue Jan 9 17:59:49 UTC 2024
built by: Cesar Talledo
oci-specs: 1.1.0+dev
The text was updated successfully, but these errors were encountered:
Yes, that's for sure a bug, thought it's strange why it occurs.
Sysbox emulates the contents of a few files under /proc/sys/kernel, but interestingly /proc/sys/kernel/random/uuid is not one of those, meaning that the access to that file within the container is eventually serviced by the Linux kernel (rather than emulated by Sysbox). So it's very strange that we see the same uuid on every invocation.
The file /proc/sys/kernel/random/uuid should respond a new uuid each time we read it.
Some applications uses this file to generate uuid and we have collisions because it responds always the same uuid.
Here is an example with runc:
Here is the result with sysbox:
Some informations:
The text was updated successfully, but these errors were encountered: