Skip to content

Conversation

@keloyang
Copy link

@keloyang keloyang commented Aug 5, 2016

I Follow the instructions(README.md), and "./test_runtime.sh -r docker-runc" execute failed. So I have this modify.

  • runc start failed if it has no runc create ,so change start to run (create+start), it will avoid "**/state.json: no such file or directory" error.
  • add --tty to command ,the generated config.json will has"terminal: true", it will avoid the "/dev/console not found" error.
    then I can see the validation.
root@ubuntu:****opencontainers/ocitools# ./test_runtime.sh -r docker-runc -l debug
-----------------------------------------------------------------------------------
VALIDATING RUNTIME: docker-runb
-----------------------------------------------------------------------------------
DEBU[0000] validating root filesystem                   
DEBU[0000] validating container process                 
DEBU[0000] validating capabilities                      
DEBU[0000] validating hostname                          
DEBU[0000] validating rlimits                           
DEBU[0000] validating mounts exist                      
DEBU[0000] validating linux default filesystem          
DEBU[0000] validating linux default devices             
DEBU[0000] validating sysctls                           
DEBU[0000] validating maskedPaths                       
DEBU[0000] validating readonlyPaths                     
Runtime docker-runb passed validation

Signed-off-by: Shukui Yang yangshukui@huawei.com

Signed-off-by: Shukui Yang <yangshukui@huawei.com>
cp runtimetest ${TESTDIR}

ocitools generate --output "${TESTDIR}/config.json" "${TEST_ARGS[@]}" --rootfs '.'
ocitools generate --tty --output "${TESTDIR}/config.json" "${TEST_ARGS[@]}" --rootfs '.'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If docker-runc failed without --tty. I think that's docker-runc's problem. The spec says /dev/console is the default device for Linux which must be supplied by runtime.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

--tty is unnecessary , add it we can see the output info,wouldn't it be better?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On 08/05/2016 04:27 PM, keloyang wrote:

--tty is unnecessary , add it we can see the output info,wouldn't it be better?

Sorry, I'm not sure what you wanted to express. more detailed?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

debug info, such as DEBU[0000] validating ...

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On 08/05/2016 05:30 PM, keloyang wrote:

debug info, such as DEBU[0000] validating ...
That is not --tty's function.
If you want info like that, you just need to execute test_runtime.sh with -l debug.
--tty is not necessary.

@wking
Copy link
Contributor

wking commented Aug 5, 2016 via email

@keloyang
Copy link
Author

keloyang commented Aug 8, 2016

thank you, I think I can close this pr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants