New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to pass options to container creation #719
Comments
Same here, I need --privileged otherwise, containers do not run. |
In general it's rather difficult to pass arbitrary option strings into the endpoint. It either needs changes in the underlying library So, for now I suggest we'd just add those options in the UI. @distefam I'm not even sure if specifying an env file is part of the Podman RESTful API. I'm not sure because their API doc frontend seems very broken in general (https://docs.podman.io/en/latest/_static/api.html#tag/containers/operation/ContainerCreateLibpod doesn't show a request body at all). Specifying an env fle also not part in podman-api rs library and also not part of the docker documentation (https://docs.docker.com/engine/api/v1.43/#tag/Container/operation/ContainerCreate). But nevertheless, we can make this a feature of Pods if you'd like create a new issue for that. @bellegarde-c We can also expose that if you'd like to create a new issue. |
There is a way to pass arguments to the command that is run in the container, however, I cannot find a way to pass options to the build command itself. Specifically, I would like to pass
--env-file
topodman-create
.The text was updated successfully, but these errors were encountered: