Revision history [back]

We have been using both indigo and kinetic inside docker for over a year, and never had any issues of that sort. I also tested roscore & on my machine now, and there's no difference between executing it on the host vs the container.

I assume it is something to do with your docker settings. Try checking your docker-compose.yml, or execute the command in a fresh container, or on a different PC. Do report back if you find the problem.

PS: I don't know that "roscore &" is very elegant, especially while developing. I would suggest keeping it in a separate terminal and occasionally restarting it to make sure that nothing is left on the parameter server etc.

We have been using both indigo and kinetic inside docker for over a year, and never had any issues of that sort. I also tested roscore & on my machine now, and there's no difference between executing it on the host vs the container.

I assume it is something to do with your docker settings. Try checking your docker-compose.yml, or execute the command in a fresh container, or on a different PC. Do report back if you find the problem.

edit: I just saw your other question. Your nodes or other trailing processes might be the issue, too.

PS: I don't know that "roscore &" is very elegant, especially while developing. I would suggest keeping it in a separate terminal and occasionally restarting it to make sure that nothing is left on the parameter server etc.