[DiscordArchive] if your docker run failed to mount the volume, i don't know for sure if you'd get an empty volume or
[DiscordArchive] if your docker run failed to mount the volume, i don't know for sure if you'd get an empty volume or
Original source
if your docker run failed to mount the volume, i don't know for sure if you'd get an empty volume or an error that halts container start, have you tried running a bash prompt in the container to confirm the files are there?
rektbyfaith
05-01-2022, 07:35 PM #1Archived author: SmilyContainer • Posted: 2022-05-01T19:35:10.285000+00:00
Original source
if your docker run failed to mount the volume, i don't know for sure if you'd get an empty volume or an error that halts container start, have you tried running a bash prompt in the container to confirm the files are there?
Original source
and considering my sqlworkbench can connect to the current non backup one.... I'm gonna assume it is working fine
rektbyfaith
05-01-2022, 07:35 PM #2Archived author: McNaughtyVerse • Posted: 2022-05-01T19:35:16+00:00
Original source
and considering my sqlworkbench can connect to the current non backup one.... I'm gonna assume it is working fine
Original source
agreed, safe assumption
rektbyfaith
05-01-2022, 07:35 PM #3Archived author: SmilyContainer • Posted: 2022-05-01T19:35:28.483000+00:00
Original source
agreed, safe assumption
Original source
and if I knew how to do all of what you just asked I wouldn't be here
rektbyfaith
05-01-2022, 07:35 PM #4Archived author: McNaughtyVerse • Posted: 2022-05-01T19:35:52.713000+00:00
Original source
and if I knew how to do all of what you just asked I wouldn't be here
Original source
btw running the command again gives me this
rektbyfaith
05-01-2022, 07:36 PM #5Archived author: McNaughtyVerse • Posted: 2022-05-01T19:36:57.670000+00:00
Original source
btw running the command again gives me this
Original source
docker: Error response from daemon: Conflict. The container name "/my-mysql" is already in use by container "01e68c94ab93d040d8b3f6e791790d2f249d6d7e92f500ba9fb8b6dc62421929". You have to remove (or rename) that container to be able to reuse that name.
rektbyfaith
05-01-2022, 07:37 PM #6Archived author: McNaughtyVerse • Posted: 2022-05-01T19:37:07.160000+00:00
Original source
docker: Error response from daemon: Conflict. The container name "/my-mysql" is already in use by container "01e68c94ab93d040d8b3f6e791790d2f249d6d7e92f500ba9fb8b6dc62421929". You have to remove (or rename) that container to be able to reuse that name.
Original source
so I'm gonna assume it's running from the first time I ran the command
rektbyfaith
05-01-2022, 07:37 PM #7Archived author: McNaughtyVerse • Posted: 2022-05-01T19:37:23.470000+00:00
Original source
so I'm gonna assume it's running from the first time I ran the command
Original source
Messaged you privately
rektbyfaith
05-01-2022, 07:38 PM #8Archived author: McNaughtyVerse • Posted: 2022-05-01T19:38:24.406000+00:00
Original source
Messaged you privately
Original source
ah ok so running a shell session in a docker container is pretty easy, im gonna defer ya to google there because i gotta step away to demolish a sandiwch, i'll check back later though
rektbyfaith
05-01-2022, 07:38 PM #9Archived author: SmilyContainer • Posted: 2022-05-01T19:38:48.489000+00:00
Original source
ah ok so running a shell session in a docker container is pretty easy, im gonna defer ya to google there because i gotta step away to demolish a sandiwch, i'll check back later though
1 Guest(s)
1 Guest(s)