Front page Forums Communities 🇨🇦 Canada 🇨🇦 Quebec 🇨🇦 Montréal 🎓 U. Montréal 🎓 U. Montréal – Fall 2018 class Runing lane following demo but cannot take a log

This topic contains 5 replies, has 3 voices, and was last updated by https://www.duckietown.org/wp-content/uploads/ap_avatars/eddea82ad2755b24c4e168c5fc2ebd40.jpg Breandan Considine 3 weeks, 6 days ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #29994

    Jon
    Participant

    Hello,

    I have been able to run the lane following demo. However when I try to run this line of code to take the log:

    docker -H mrquackers.local run -it –net host –name logger -v /data/logs:/logs duckietown/rpi-duckiebot-logger:master18

    I get this error:

    docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused “exec: \”/ros_entrypoint.sh\”: stat /ros_entrypoint.sh: no such file or directory”: unknown.

    The logger container has status created on the portainer but I cannot run it.

    Thanks,

    Jon

    #29995
    https://www.duckietown.org/wp-content/uploads/ap_avatars/1679091c5a880faf6fb5e6087eb1b2dc.jpg
    Liam Paull
    Keymaster

    ok – this is easily my least favorite bug – seen it so many times but never really sure how to fix.

    It’s almost always related to the ARM emulation. You might try adding –entrypoint=qemu-arm-static, but I fear it will not fix it.

    #29996

    Jon
    Participant

    I ran
    $ docker -H mrquackers.local run -it –net host –name logger -entrypoint=qemu-arm-static -v /data/logs:/logs duckietown/rpi-duckiebot-logger:master18

    and I still got the same error

    docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused “exec: \”/ros_entrypoint.sh\”: stat /ros_entrypoint.sh: no such file or directory”: unknown.

    Did I run the command correctly?

    #30000
    https://www.duckietown.org/wp-content/uploads/ap_avatars/eddea82ad2755b24c4e168c5fc2ebd40.jpg
    Breandan Considine
    Participant

    We never did get to the bottom of this yesterday. Either there are some old images that are corrupting the cache, or something is broken about the Docker daemon. Our solution was to re-flash the SD card and the issue disappeared. Same image hash, same version of Docker, same command. --entrypoint=qemu-arm-static is not necessary.

    edit: Jon, if you bring the Duckiebot into the lab today I can try to diagnose the issue to see what might be the cause. Perhaps others will have the same issue and we should troubleshoot more carefully. Thanks for your patience.

    #30002

    Jon
    Participant

    I will bring it tomorrow morning. Is that okay?

    Thanks,

    Jon

    #30003
    https://www.duckietown.org/wp-content/uploads/ap_avatars/eddea82ad2755b24c4e168c5fc2ebd40.jpg
    Breandan Considine
    Participant

    Sure, let’s take a look at this tomorrow before class.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.

Close Menu