Open rafaismyname opened 5 years ago
Hi @rafaismyname
Hm. It's strange.
Did you create .env
file with COMPOSE_PROJECT_NAME param before project importing?
Also I need additional info
1) What are names have got containers if you run a project via terminal
2) What are names have got containers if you run the project via DockStation
@igor-lemon
Nope i have not set the COMPOSE_PROJECT_NAME
param, i just ran docker-compose up
and got my env up and running.
1- If i run via terminal, container's names would be the name of the docker-compose.yml
file's folder. Ex.: Path of my project being \Users\Rafa\Dev\Project
the name of the containers would be project_[serviceName]_[instanceCount]
(project_database_1
)
2- If starting the imported docker-compose.yml
using Dockstation, it will create another containers (not re-utilizing the ones that were already created for that compose project) using the proper naming that Dockstation implies
Let me know if you need any other info. :)
Best regards
1) What is name of containers which was created via DockStation? 2) Can you show me your docker-compose config? You can write to igor@dockstation.io
Hello there!
First of all, thanks for this awesome product! :)
I have a docker-compose project that was already up-and-running before installing DockStation. After running dockstation and creating a new project, by importing an existing compose-file, dockstation shows the project as stopped, even tho it's currently running. Also, if I choose to start the "allegedly stopped" project, dockstation tries to recreate all containers, volumes, networks, etc...
How can i create an "imported" project and having it already "attached" to my existing docker-compose's containers(and its status)/volumes/networks/etc?
I'm using macOS, my dockstation version is 1.5.1, docker-engine is 18.09.02 and docker-compose is 1.23.2.
Best regards