Closed googlielmo closed 8 years ago
This sounds related to https://github.com/brooklyncentral/clocker/issues/267
Yes, that's what I was thinking @aledsage - will investigate further later
Should be fixed by commit ab0a29e5084ba2603c66cd4ca5b92c9102940647
When creating a Docker host on a location having
installDevUrandom=true
, the/dev/random
device node is not found to be a symbolic link to/dev/urandom
. This may affect SSH and/or Clocker performance.Evidence suggests that the VM is provisioned correctly to begin with, but then a kernel update takes place, and this has the effect to revert all of the '/dev' device nodes to their pristine state.
To prove this, I provisioned an Ubuntu VM from Brooklyn with that flag set, and manually installed the same kernel as Clocker does at https://github.com/brooklyncentral/clocker/blob/d7d7d6c866cc4bcee1d7df9e238c002e3f10e912/docker/src/main/java/brooklyn/entity/container/docker/DockerHostSshDriver.java#L195
This is what I get: