Open dabro opened 7 years ago
What problem do you have with docker-compose
?
I am already using this library for the containers managed by compose, and it works just fine
Maybe the confusion here is between the service name and the container name (as mentioned box
vs dev_box_1
). However this is not a problem and the package works no problem so long as the container name is used.
It would be nice to maybe map to the service name but then I call everything app
so that would likely result in more confusion than good.
If you always want names (rather than the container IDs) to appear in the completion list then (setq docker-tramp-use-names t)
How would you suggest best using or modifying this package to use containers that are managed by docker-compose, which move a lot of configuration/env/dependency settings to the
docker-compose.yml
file? There is of coursedocker-compose exec
, whose big difference is the lack of-e
and the default tty allocation. But you also have to account for thedocker-compose
options, like-p
to specify a non-defaultdocker-compose.yml
file, and the difference between the docker name (egdev_box_1
) and the docker-compose service name (egbox
):There's also
docker-compose run
: