dispacher mounts wrong directory into user-agent
cz8s opened this issue · comments
when starting a user-agent inside docker, the dispatcher wants to mount the wron directory into it:
2015-09-15T20:59:58.352474+02:00 pixelated pixelated.proxy: INFO Starting agent for giovane
2015-09-15T20:59:59.237804+02:00 pixelated pixelated.manager: ERROR Unhandled Error during request: 500 Server Error: Internal Server Error ("Cannot start container 256bb060e9d72227f91c3cb88a9ed98705c27540fbe47cfb3bac1c8a99755c3d: setup mount namespace bind mounts stat /var/lib/pixelated/dispatcher/kaeff/data: no such file or directory")
so giovane logs in and the dispatcher wants to mount the user-dir from kaeff.
That seems to be wrong ...
very reproducable:
2015-09-15T21:24:12.902763+02:00 pixelated pixelated.proxy: INFO Starting agent for iamnotkaeff
2015-09-15T21:24:13.913778+02:00 pixelated pixelated.manager: ERROR Unhandled Error during request: 500 Server Error: Internal Server Error ("Cannot start container 256bb060e9d72227f91c3cb88a9ed98705c27540fbe47cfb3bac1c8a99755c3d: setup mount namespace bind mounts stat /var/lib/pixelated/dispatcher/kaeff/data
on wazozokazi. we had an image on wazokazi which had a volume mount for kaeff.
It was also named pixelated-user-agent and thats why it was used for new users on wazokazi.
removing that image solved the problem.
Question: why did we have that on wazokazi? did anybody run the tests there?
