search

sea-bass / turtlebot3_behavior_demos

Example repository for autonomous behaviors using TurtleBot3, as well as Docker workflows in ROS based projects.
MIT License
270 stars 53 forks source link

docker compose build isn't working #36

Open vipermn opened 1 year ago

vipermn commented 1 year ago

I am getting these errors messages after doing a docker compose build.

BLIRKSPR MINGW64 ~/dockerimage/turtlebot3_behavior_demos/docker (main) $ docker compose up overlay Container turtlebot3_behavior_demos-overlay-1 Creating Container turtlebot3_behavior_demos-overlay-1 Created Attaching to turtlebot3_behavior_demos-overlay-1 turtlebot3_behavior_demos-overlay-1 | exec /entrypoint.sh: no such file or directory turtlebot3_behavior_demos-overlay-1 exited with code 1

BLIRKSPR MINGW64 ~/dockerimage/turtlebot3_behavior_demos/docker (main) $ docker compose up sim Container turtlebot3_behavior_demos-sim-1 Creating Container turtlebot3_behavior_demos-sim-1 Created Attaching to turtlebot3_behavior_demos-sim-1 turtlebot3_behavior_demos-sim-1 | exec /entrypoint.sh: no such file or directory turtlebot3_behavior_demos-sim-1 exited with code 1

BLIRKSPR MINGW64 ~/dockerimage/turtlebot3_behavior_demos/docker (main) $ docker compose up dev Container turtlebot3_behavior_demos-dev-1 Creating Container turtlebot3_behavior_demos-dev-1 Created Attaching to turtlebot3_behavior_demos-dev-1 turtlebot3_behavior_demos-dev-1 | exec /entrypoint.sh: no such file or directory turtlebot3_behavior_demos-dev-1 exited with code 1

It looks like everything built okay when the docker compose build command was issued.

Output file attached. dockerbuildissue.txt

sea-bass commented 1 year ago

I notice you are running the commands from the turtlebot3_behavior_demos/docker folder.

Can you do it from one folder up? So from ~/dockerimage/turtlebot3_behavior_demos?

vipermn commented 1 year ago

I rebuilt the image and ran from one folder up as you suggested. No change.

BLIRKSPR MINGW64 ~/dockerimage/turtlebot3_behavior_demos (main) $ docker compose up dev Container turtlebot3_behavior_demos-dev-1 Creating Container turtlebot3_behavior_demos-dev-1 Created Attaching to turtlebot3_behavior_demos-dev-1 turtlebot3_behavior_demos-dev-1 | exec /entrypoint.sh: no such file or directory turtlebot3_behavior_demos-dev-1 exited with code 1

BLIRKSPR MINGW64 ~/dockerimage/turtlebot3_behavior_demos (main) $ docker compose up sim Container turtlebot3_behavior_demos-sim-1 Creating Container turtlebot3_behavior_demos-sim-1 Created Attaching to turtlebot3_behavior_demos-sim-1 turtlebot3_behavior_demos-sim-1 | exec /entrypoint.sh: no such file or directory turtlebot3_behavior_demos-sim-1 exited with code 1

MINGW64 ~/dockerimage/turtlebot3_behavior_demos (main) $ docker compose up overlay Container turtlebot3_behavior_demos-overlay-1 Creating Container turtlebot3_behavior_demos-overlay-1 Created Attaching to turtlebot3_behavior_demos-overlay-1 turtlebot3_behavior_demos-overlay-1 | exec /entrypoint.sh: no such file or directory turtlebot3_behavior_demos-overlay-1 exited with code 1

sea-bass commented 1 year ago

Did you also rebuild it from one folder up? I just grabbed the latest version of this repo and it ran fine...

vipermn commented 1 year ago

I did rebuild it from one folder up.

Here is a list of the images after docker compose build: $ docker images -a REPOSITORY TAG IMAGE ID CREATED SIZE turtlebot3_behavior dev ecce2df38351 30 seconds ago 5.15GB

661f11619881 47 seconds ago 5.07GB turtlebot3_behavior overlay a453b643c750 47 seconds ago 5.07GB bffe6fc33c93 47 seconds ago 5.07GB f6e44abcfdc0 47 seconds ago 5.07GB ed6377f59c45 47 seconds ago 5.07GB turtlebot3_behavior base 7e4c04859872 3 minutes ago 4.72GB Note: I am building this on Windows 10 with Docker Desktop running Version 4.21.1 (114176) which has Compose v2.19.1 in it. It fails to start using either the command line or from with the Docker Desktop GUI.
sea-bass commented 1 year ago

AHA! The Windows host might do it... I wonder if it's something related to this: https://stackoverflow.com/questions/38905135/why-wont-my-docker-entrypoint-sh-execute

Maybe the docker/entrypoint.sh file I put up on GitHub doesn't play nicely with Windows hosts machines at build time. Might be worth trying to see if you can locally make updates to that file pre-building?