pasa
04/09/2018, 7:49 PMsudo docker run --name=prisma-db --network local_prisma -e MYSQL_ROOT_PASSWORD=graphcool -d mysql:5.7
to create the mysql container by hand, it just says, that it already exists, which is true.
Here is the exact output from the console:
docker: Error response from daemon: Conflict. The container name "/prisma-db" is already in use by container "b9e41092f086780c7a4c22ba1653eae7ceed1d9c6c3a4cec347f5d91615e8741". You have to remove (or rename) that container to be able to reuse that name.
@nilan How should I progress from here on?pasa
04/10/2018, 7:17 AMBooting local development cluster !
! Recreating local_prisma-database_1 ...
Starting prisma-db ... error
!
! ERROR: for prisma-db Cannot start service prisma-db: driver failed programming external connectivity on endpoint prisma-db
Recreating local_prisma-database_1 ... error
! /port/tcp:0.0.0.0:3307:tcp:172.18.0.2:3306: input/output error
!
! ERROR: for local_prisma-database_1 Cannot start service prisma-database: driver failed programming external connectivity on
! endpoint local_prisma-database_1 (fa147255f06964d28b44d51c16ac97b6b6a3e9b32dd53113dbc13546471fda84): Error starting userland
! proxy: mkdir /port/tcp:0.0.0.0:4466:tcp:172.18.0.2:4466: input/output error
!
! ERROR: for prisma-db Cannot start service prisma-db: driver failed programming external connectivity on endpoint prisma-db
! (c4a8594cdc7f59ff55643012d17187834ee5d204a214e47365903f458f518f0d): Error starting userland proxy: mkdir
! /port/tcp:0.0.0.0:3307:tcp:172.18.0.2:3306: input/output error
!
! ERROR: for prisma-database Cannot start service prisma-database: driver failed programming external connectivity on endpoint
! local_prisma-database_1 (fa147255f06964d28b44d51c16ac97b6b6a3e9b32dd53113dbc13546471fda84): Error starting userland proxy: mkdir
! /port/tcp:0.0.0.0:4466:tcp:172.18.0.2:4466: input/output error
! Encountered errors while bringing up the project.
nilan
04/10/2018, 7:30 AMpasa
04/10/2018, 7:54 AMprisma init
after deleting ALL local containers.andre
04/10/2018, 8:18 AMdocker kill prisma-db && docker rm prisma-db
and try a prisma deploy
afterwards? This should help in this regard.andre
04/10/2018, 8:19 AMkill
will kill your MySQL container and the rm
will remove the stopped container afterwards. Prisma asserts a name to the container which leads to the exception above when trying to boot the cluster when the database is already running.