mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-08-01 15:57:20 +00:00
agent: always try to override oci process spec
In previous version, only when the `guest-pull` feature is enabled during the build time, the OCI process will be tried to be overrided when the storage has a guest pull volume and also it is sandbox. After getting rid of the feature, whether it is guest-pull is runtimely determined thus we can always do this trying override, by checking if there is kata guest pull volume in storages and it's sandbox. Signed-off-by: Xynnn007 <xynnn@linux.alibaba.com>
This commit is contained in:
parent
6b1249186f
commit
105cb47991
@ -312,19 +312,14 @@ impl AgentService {
|
|||||||
|
|
||||||
let pipe_size = AGENT_CONFIG.container_pipe_size;
|
let pipe_size = AGENT_CONFIG.container_pipe_size;
|
||||||
|
|
||||||
let p = if let Some(p) = oci.process() {
|
let Some(p) = oci.process() else {
|
||||||
{
|
|
||||||
let new_p =
|
|
||||||
confidential_data_hub::image::get_process(p, &oci, req.storages.clone())?;
|
|
||||||
Process::new(&sl(), &new_p, cid.as_str(), true, pipe_size, proc_io)?
|
|
||||||
}
|
|
||||||
|
|
||||||
Process::new(&sl(), p, cid.as_str(), true, pipe_size, proc_io)?
|
|
||||||
} else {
|
|
||||||
info!(sl(), "no process configurations!");
|
info!(sl(), "no process configurations!");
|
||||||
return Err(anyhow!(nix::Error::EINVAL));
|
return Err(anyhow!(nix::Error::EINVAL));
|
||||||
};
|
};
|
||||||
|
|
||||||
|
let new_p = confidential_data_hub::image::get_process(p, &oci, req.storages.clone())?;
|
||||||
|
let p = Process::new(&sl(), &new_p, cid.as_str(), true, pipe_size, proc_io)?;
|
||||||
|
|
||||||
// if starting container failed, we will do some rollback work
|
// if starting container failed, we will do some rollback work
|
||||||
// to ensure no resources are leaked.
|
// to ensure no resources are leaked.
|
||||||
if let Err(err) = ctr.start(p).await {
|
if let Err(err) = ctr.start(p).await {
|
||||||
|
Loading…
Reference in New Issue
Block a user