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
Ideally we want to capture the computational environment of the container and the host using the computational environment pattern context (https://github.com/Vocamp/ComputationalActivity/blob/master/pattern/ComputationalEnvironment.jsonld). The issue is that our knowledge of the host may be limited since we don't have a direct API hook to the environment other than container architecture, os and size. This limits the amount of information we can provide in the pattern, although a container is limited to the number of cores, memory and storage available on the host machine. This is a limitation of our knowledge of the docker engine.
Ideally we want to capture the computational environment of the container and the host using the computational environment pattern context (https://github.com/Vocamp/ComputationalActivity/blob/master/pattern/ComputationalEnvironment.jsonld). The issue is that our knowledge of the host may be limited since we don't have a direct API hook to the environment other than container architecture, os and size. This limits the amount of information we can provide in the pattern, although a container is limited to the number of cores, memory and storage available on the host machine. This is a limitation of our knowledge of the docker engine.
The text was updated successfully, but these errors were encountered: