I am trying to run a simulation environment as well as robot model which I didn’t build it. So I dowlanded Docker Desktop on my Windows Home 10 and try to run this container called ayas-gazebo-1. In this container. It is supposed to run VNC and GZweb envireonment on the localhost via ports 8081 and 8080 respectively. While VNC environment seem to be workin fine, in GZweb the map isn’t loading(only seeing empty grid). As you can see on the screenshots
VNC Environment on localhost 8081
Note: also you can observe that Robot Model isn’t recieving properly as well as the camera data.
I have been trying to run again and again container ayas-gazebo-1 but it seem to be having same problem. But I am not sure what kind of problem that I am facing.
Also I am attaching ayas-gazebo-1 container’s logs which I got from Docker Desktop.
ln: failed to create symbolic link '/usr/bin/python': File exists
File "/home/catkin_ws/src/CMakeLists.txt" already exists[WARN tini (72)] Tini is not running as PID 1 and isn't registered as a child subreaper.
[ 0%] Built target kangal_description_xacro_generated_to_devel_space_
[ 0%] Built target kangal_world_xacro_generated_to_devel_space_
[ 75%] Built target hakan_plugin
[ 75%] Built target traffic_light_plugin
[ 75%] Built target gazebo_ros_velodyne_gpu_laser
[100%] Built target gazebo_ros_velodyne_laser
Base path: /home/catkin_ws
Source space: /home/catkin_ws/src
Build space: /home/catkin_ws/build
Devel space: /home/catkin_ws/devel
Install space: /home/catkin_ws/install
####
#### Running command: "make cmake_check_build_system" in "/home/catkin_ws/build"
####
####
#### Running command: "make -j12 -l12" in "/home/catkin_ws/build"
####
2023-09-14 04:02:37,563 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2023-09-14 04:02:37,564 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2023-09-14 04:02:37,889 INFO RPC interface 'supervisor' initialized
2023-09-14 04:02:37,889 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-09-14 04:02:37,889 INFO supervisord started with pid 75
2023-09-14 04:02:38,892 INFO spawned: 'nginx' with pid 77
2023-09-14 04:02:38,906 INFO spawned: 'web' with pid 78
2023-09-14 04:02:38,911 INFO spawned: 'xvfb' with pid 79
2023-09-14 04:02:38,926 INFO spawned: 'wm' with pid 80
2023-09-14 04:02:38,942 INFO spawned: 'lxpanel' with pid 81
2023-09-14 04:02:38,956 INFO spawned: 'pcmanfm' with pid 82
2023-09-14 04:02:38,975 INFO spawned: 'x11vnc' with pid 83
2023-09-14 04:02:38,990 INFO spawned: 'novnc' with pid 84
2023-09-14 04:02:39,002 INFO spawned: 'lxteminal' with pid 85
2023-09-14 04:02:39,017 INFO spawned: 'bashrc' with pid 86
2023-09-14 04:02:39,022 INFO spawned: 'bashgazebo' with pid 87
2023-09-14 04:02:39,036 INFO spawned: 'bashgzweb' with pid 89
2023-09-14 04:02:39,053 INFO exited: xvfb (exit status 1; not expected)
2023-09-14 04:02:39,112 INFO exited: wm (exit status 1; not expected)
2023-09-14 04:02:39,144 INFO exited: lxpanel (exit status 1; not expected)
2023-09-14 04:02:39,145 INFO exited: pcmanfm (exit status 1; not expected)
2023-09-14 04:02:39,254 INFO exited: lxteminal (exit status 1; not expected)
2023-09-14 04:02:40,088 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:40,089 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:40,092 INFO spawned: 'xvfb' with pid 206
2023-09-14 04:02:40,093 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:40,093 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:40,093 INFO success: bashrc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:40,093 INFO success: bashgazebo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:40,094 INFO success: bashgzweb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:40,107 INFO exited: x11vnc (exit status 1; not expected)
2023-09-14 04:02:40,184 INFO spawned: 'wm' with pid 209
2023-09-14 04:02:40,196 INFO spawned: 'lxpanel' with pid 215
2023-09-14 04:02:40,203 INFO spawned: 'pcmanfm' with pid 221
2023-09-14 04:02:40,214 INFO spawned: 'x11vnc' with pid 229
2023-09-14 04:02:40,288 INFO spawned: 'lxteminal' with pid 237
2023-09-14 04:02:40,543 INFO Listening on http://localhost:6079 (run.py:87)
2023-09-14 04:02:41,248 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:41,250 INFO success: wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:41,250 INFO success: lxpanel entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:41,250 INFO success: pcmanfm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:41,250 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-14 04:02:41,285 INFO success: lxteminal entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.