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
{{ message }}
This repository has been archived by the owner on Jun 2, 2022. It is now read-only.
Kubernetes containers should follow a similar format to docker containers:
log
metadata.json
fs/
If we can't access the log due to permissions issues, we can omit the log file.
The implementation should look similar to https://github.com/puppetlabs/wash/blob/master/plugin/docker/container.go, where we list 'log' and 'metadata' entries for the pod, implement metadata for the pod, and then add pod_metadata and pod_log implementations to implement the files using references back to the pod. Also use the volume helpers to expose the filesystem.
The text was updated successfully, but these errors were encountered:
We now always specify the stdin parameter if we expect to pass a stdin
io.Writer. This causes tty=true invocations to hang and timeout, but we
never call it with a tty (until puppetlabs-toy-chest#203).
Signed-off-by: Michael Smith <[email protected]>
Change the Kubernetes container entry to a directory mirroring the
Docker container structure: log, metadata, filesystem.
Also fixes using a tty with the container's exec method (which was
previously unused).
Resolvespuppetlabs-toy-chest#203.
Signed-off-by: Michael Smith <[email protected]>
Kubernetes containers should follow a similar format to docker containers:
If we can't access the log due to permissions issues, we can omit the
log
file.The implementation should look similar to https://github.com/puppetlabs/wash/blob/master/plugin/docker/container.go, where we list 'log' and 'metadata' entries for the pod, implement metadata for the pod, and then add pod_metadata and pod_log implementations to implement the files using references back to the pod. Also use the volume helpers to expose the filesystem.
The text was updated successfully, but these errors were encountered: