Restarting server with docker-compose may crash with "Are you trying to mount a directory onto a file (or vice-versa)?"

[Rikuoja]

Describe the bug
In some cases, restarting serve with docker-compose when services have been started in the wrong order may fail with

ERROR: for swag  Cannot start service serve: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/tmp/flask/uwsgi.sock" to rootfs at "/tmp/flask/uwsgi.sock" caused: mount through procfd: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

To Reproduce
Will be caused at least by /tmp/flask/uwsgi.sock being directory instead of socket. This may be caused by starting the services in the wrong order, so mounting has created it, instead of flask, as it should. Also may be caused by stale/old volumes available to swag image?

Additional context
Related to docker-compose issue docker-archive/compose-cli#1795

May be fixed by

1. rmdir /tmp/flask/uwsgi.sock, so flask will recreate it as socket, and
2. deleting swag volumes with docker-compose rm -v serve