Closed DavidNY123 closed 1 year ago
this problem is caused by you got two '-v' with the first '-v' without any parameter, may have to check whether is the issue with your local script(maybe accidently modified something).
this problem is caused by you got two '-v' with the first '-v' without any parameter, may have to check whether is the issue with your local script(maybe accidently modified something).
OH!, I change the {workspace_mount} = "", because I noticed the comments in the d2vin.yaml
So, here got two '-v' with the first '-v' without any parameter.
Hi,when I want to evaluate multir-robot datasets on my PC with docker, I have met a strange problem.
rosrun sync_bag_player docker_swarm_test.py /home/mwy/BAG/D2SLAM/tum_corr/d2vins.yaml
Start swarm docker test Launching docker swarm1 docker run --name swarm1_319961 --gpus all --rm -it -v -v /home/mwy/BAG/D2SLAM/tum_corr/outputs/d2vins/swarm1:/root/output/ -v /home/mwy/BAG/D2SLAM/tum_corr/Configs:/root/SwarmConfig/ -v /home/mwy/BAG/D2SLAM/tum_corr/d2vins.yaml:/root/config.yaml -v /home/mwy/BAG/D2SLAM/tum_corr:/root/bags/ -v /tmp/swarm1_319961_entry_point.sh:/root/entry_point.sh -v /home/mwy/D2SLAM_sync_bag_player/src/sync_bag_player/scripts/docker_entrypoint.sh:/root/docker_entrypoint.sh --env='DRONE_ID=1' --env='DISPLAY' --volume='/tmp/.X11-unix:/tmp/.X11-unix:rw' --privileged d2slam:pc /root/docker_entrypoint.sh /root/bags/dataset-corridor1_512_16-sync-comp.bag 319961 Launching docker swarm2 docker run --name swarm2_319961 --gpus all --rm -it -v -v /home/mwy/BAG/D2SLAM/tum_corr/outputs/d2vins/swarm2:/root/output/ -v /home/mwy/BAG/D2SLAM/tum_corr/Configs:/root/SwarmConfig/ -v /home/mwy/BAG/D2SLAM/tum_corr/d2vins.yaml:/root/config.yaml -v /home/mwy/BAG/D2SLAM/tum_corr:/root/bags/ -v /tmp/swarm2_319961_entry_point.sh:/root/entry_point.sh -v /home/mwy/D2SLAM_sync_bag_player/src/sync_bag_player/scripts/docker_entrypoint.sh:/root/docker_entrypoint.sh --env='DRONE_ID=2' --env='DISPLAY' --volume='/tmp/.X11-unix:/tmp/.X11-unix:rw' --privileged d2slam:pc /root/docker_entrypoint.sh /root/bags/dataset-corridor2_512_16-sync-comp.bag 319961 Launching docker swarm3 docker run --name swarm3_319961 --gpus all --rm -it -v -v /home/mwy/BAG/D2SLAM/tum_corr/outputs/d2vins/swarm3:/root/output/ -v /home/mwy/BAG/D2SLAM/tum_corr/Configs:/root/SwarmConfig/ -v /home/mwy/BAG/D2SLAM/tum_corr/d2vins.yaml:/root/config.yaml -v /home/mwy/BAG/D2SLAM/tum_corr:/root/bags/ -v /tmp/swarm3_319961_entry_point.sh:/root/entry_point.sh -v /home/mwy/D2SLAM_sync_bag_player/src/sync_bag_player/scripts/docker_entrypoint.sh:/root/docker_entrypoint.sh --env='DRONE_ID=3' --env='DISPLAY' --volume='/tmp/.X11-unix:/tmp/.X11-unix:rw' --privileged d2slam:pc /root/docker_entrypoint.sh /root/bags/dataset-corridor3_512_16-sync-comp.bag 319961 docker: invalid reference format: repository name must be lowercase. See 'docker run --help'. docker: invalid reference format: repository name must be lowercase. See 'docker run --help'. docker: invalid reference format: repository name must be lowercase. See 'docker run --help'. ^CKeyboardInterrupt Error response from daemon: Cannot kill container: swarm1_319961: No such container: swarm1_319961 Error response from daemon: Cannot kill container: swarm2_319961: No such container: swarm2_319961 Error response from daemon: Cannot kill container: swarm3_319961: No such container: swarm3_319961
I think this docker container name id valid ,and In the previous several runs, the terminal didn't indicate any issues with the names of the Docker containers. However, the instantiated containers had empty 'swarm_ws' directories, which prevented subsequent operations. Strangely enough, after a certain test, the terminal suddenly started pointing out problems with the Docker container names.