Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

guest OCI hooks failed to find config.json #873

Closed
chestack opened this issue Dec 28, 2020 · 1 comment
Closed

guest OCI hooks failed to find config.json #873

chestack opened this issue Dec 28, 2020 · 1 comment
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.

Comments

@chestack
Copy link

chestack commented Dec 28, 2020 •
edited
Loading

Description of problem

Run kata pod with nvidia GPU:

  1. Created a rootfs with nvidia-container-toolkit located in /usr/share/oci/hooks/prestart/
  2. Enabled guest_hook_path = "/usr/share/oci/hooks" in the configuration.toml.
  3. Run pod with gpu resource

Expected result

container should start and hooks should run

Actual result

container started with the following error:
level=error msg="createContainer failed" error="rpc error: code = Internal desc = Could not run process: container_linux.go:349: starting container process caused \"process_linux.go:449: container init caused \\\"process_linux.go:432: running prestart hook 0 caused \\\\\\\"error running hook: exit status 1, stdout: , stderr: could not open OCI spec: open /run/kata-containers/shared/containers/e882de8a1f87e4b831b54c0617e00554a52fa01acdb58c61dacba0152848aee1/config.json: no such file or directory\\\\\\\\n\\\\\\\"\\\"\"" source=virtcontainers subsystem=kata_agent

Further information

writeSpecToFile() and changeToBundlePath() in #393 write config.json to /run/kata-containers/shared/containers/***

but writeSpecToFile() in #798 updated to change dir to /var/run/libcontainer/***
@chestack chestack added bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Dec 28, 2020
@chestack chestack mentioned this issue Dec 28, 2020
Closed
@fidencio
Copy link
Member

This issue is being automatically closed as Kata Containers 1.x has now reached EOL (End of Life). This means it is no longer being maintained.

Important:

All users should switch to the latest Kata Containers 2.x release to ensure they are using a maintained release that contains the latest security fixes, performance improvements and new features.

This decision was discussed by the @kata-containers/architecture-committee and has been announced via the Kata Containers mailing list:

If you believe this issue still applies to Kata Containers 2.x, please open an issue against the Kata Containers 2.x repository, pointing to this one, providing details to allow us to migrate it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Change dir to config.json located path before running hooks chestack/agent-1
2 participants
@fidencio @chestack