Mario Loriedo
Mario Loriedo
/remove-lifecycle stale
> @amisevsk That makes sense as to another way to secure, but that breaks a lot of the containers in the workspace that can't be nested under paths and require...
@baude at minimum we should be consistent (`podman info` and `podman machine ls` should return the same values) and ideally we should always show the values that are currently returned...
It looks like in podman we are [not parsing sbom command line arguments](https://github.com/containers/podman/blob/b8a9b184afbc13c68d34185a60ad3dd89e6160f7/cmd/podman/common/build.go#L271) and [that's done buildah CLI side](https://github.com/containers/podman/blob/286fbf98d15c85723a9e90349431aaaa56f16078/vendor/github.com/containers/buildah/pkg/cli/build.go#L332). Should not be related to WSL or Kube.
@AndreiPaulau would you like to submit a PR to fix this?
This issue has been mentioned by [this PR](https://github.com/containers/podman/pull/23894) that tries to fix it. The right way to solve this would be to package and send the images-named folders and context-dir...
> This would partially address some of my use cases, but I would not be able to continue using podman from inside a dev-container, the solution provided would not fix...
@odockal I think you should create a VM using something other than `podman machine init` (vagrant, maybe?). Or find a way to test a remote connection without manually deleting the...
@danegsta thank you! I believe changes to `go.mod` and the vendor folder should not be part of this PR.