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

cli: add no-pivot flag to be compatible with docker in ramdisk #412

Closed
wants to merge 3 commits into from
Closed

Conversation

wwq2333
Copy link
Contributor

@wwq2333 wwq2333 commented Jun 19, 2018

This commit add a no-pivot flag (just a warning tip) in kata-runtime create and run cmd.

Fixes: #409 , #134

Signed-off-by: wenqi wang [email protected]

@katacontainersbot
Copy link
Contributor

PSS Measurement:
Qemu: 142488 KB
Proxy: 4714 KB
Shim: 8885 KB

Memory inside container:
Total Memory: 2045972 KB
Free Memory: 2007308 KB

@WeiZhang555
Copy link
Member

Good PR! CI is failing because of issue below:

ERROR: Commit 10e862c30fe1705dec6ac97d46630bb31227d9d5: Failed to find subsystem in subject: "add no-pivot flag  to be compatible with docker in ramdisk"

That means you need to modify the commit message title to:
"cli: add no-pivot flag to be compatible with docker in ramdisk"

And the message body should contain detailed description, so the full commit message should looks like:

cli: add no-pivot flag  to be compatible with docker in ramdisk

Fixes: #409 , #134

This commit add a no-pivot flag (just a warning tip) in kata-runtime create and run cmd.

@jodh-intel
Copy link
Contributor

Thanks for raising @wwq19920405!

Once this lands and the feature works, we need to do two further things:

If you'd like to work on either of those issues, just add a comment on the issue, otherwise the team will look at them when they can...

@wwq2333 wwq2333 changed the title add no-pivot flag to be compatible with docker in ramdisk cli: add no-pivot flag to be compatible with docker in ramdisk Jun 19, 2018
@wwq2333
Copy link
Contributor Author

wwq2333 commented Jun 19, 2018

I meet a new problem:
docker run --runtime kata-runtime --rm busybox echo 'hello'
docker: Error response from daemon: OCI runtime create failed: rpc error: code = InvalidArgument desc = Unknown storage driver "ephemeral": unknown.


with the origin kata-runtime
docker run --runtime kata-runtime-old --rm busybox echo 'hello'
docker: Error response from daemon: OCI runtime create failed: flag provided but not defined: -no-pivot: unknown.

with kata-runtime Compiled in 5.31
docker run --runtime kata-runtime-fix --rm busybox echo 'hello'
hello

Compiled in kata-runtime latest code (6.19)
docker run --runtime kata-runtime-new --rm busybox echo 'hello'
docker: Error response from daemon: OCI runtime create failed: rpc error: code = InvalidArgument desc = Unknown storage driver "ephemeral": unknown.

@grahamwhaley
Copy link
Contributor

I think I hit the 'no ephemeral' issue last week - have a look at #394 The problem for me was my agent in my image was too old - I had to add a newly built agent to my osbuilder image.

@jodh-intel
Copy link
Contributor

That's right. If you build a rootfs using osbuilder, it will pull in the latest agent to resolve this issue:

@wwq2333
Copy link
Contributor Author

wwq2333 commented Jun 19, 2018

I didn't build a rootfs using osbuilder, just replace the kata-runtime and rum docker run cmd.
And i update all components, the problem isn't solved.

@jodh-intel
Copy link
Contributor

Hi @wwq19920405 - what we mean is that the runtime code recently added support for ephemeral volumes. Since you have built a newer version of the runtime (which includes that ephemeral support and which requires the agent to understand ephemeral volumes) you will need to to create a new rootfs image to overcome that error.

@jodh-intel
Copy link
Contributor

By the way, what are 5.31 and 6.19? I'm assuming they are dates? 😄

If so, it would be much clearer to specify them in ISO 8601 format so it is clear to all (2018-05-31 and 2018-06-19)

@wwq2333
Copy link
Contributor Author

wwq2333 commented Jun 19, 2018

They are dates, and maybe using commit id to to represent the code versions is clearer.

Since you have built a newer version of the runtime (which includes that ephemeral support and which requires the agent to understand ephemeral volumes) you will need to to create a new rootfs image to overcome that error.

I will try it, thx.

@sboeuf
Copy link

sboeuf commented Jun 19, 2018

@wwq19920405 please sign your commit and include the Fixes #... into the commit message.

@jodh-intel
Copy link
Contributor

Yep - if you look at the Travis log, you'll see what the problem is and the log will point you to:

@katacontainersbot
Copy link
Contributor

PSS Measurement:
Qemu: 146178 KB
Proxy: 4660 KB
Shim: 8898 KB

Memory inside container:
Total Memory: 2045972 KB
Free Memory: 2007432 KB

@wwq2333
Copy link
Contributor Author

wwq2333 commented Jun 20, 2018

so sorry, i delete my repository. (This my first time to submit PR on GitHub, and it is not standard enough.)

I raise a new PR #423 .

@wwq2333 wwq2333 closed this Jun 20, 2018
GabyCT added a commit to GabyCT/documentation that referenced this pull request Nov 8, 2018
Now that kata-containers/runtime#412 has been merged and
we have running a docker integration test for ramdisk in our CI
kata-containers/tests#446, we can remove the limitation
of ramdisk.

Fixes kata-containers#170

Signed-off-by: Gabriela Cervantes <[email protected]>
zklei pushed a commit to zklei/runtime that referenced this pull request Jun 13, 2019
…eMem

grpc: sandbox: add container when is fully created.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants