SEEK with Docker and unknown container "gallant_carson"

4 views
Skip to first unread message

Maria Sorokina

unread,
Mar 14, 2019, 10:33:55 AM3/14/19
to SEEK Developers
Dear all,

I am writing here to ask if anyone was/is in a similar situation.

I am running SEEK with docker-compose on my local server. Two days ago, I noticed a container that I never launched, and that was not launched by anyone else having access to this machine.
This container is named "galland_cason" and it's entry point command is ""tar cvf /backup/seek-backup.tar /seek/filestore /seek/tmp/cache" " - this is why I am supposing that it can be SEEK-related and I'm writing here.
It was also quite difficult to kill it, even with a sudo. I didn't get any non-allowed connections to my servers meanwhile.

Have you encountered the same problem? Or do you have any clue of the direction in which I should lead my investigation? 

Kind regards,

Maria Sorokina



Stuart Owen

unread,
Mar 14, 2019, 10:42:40 AM3/14/19
to seek-de...@googlegroups.com

Hi,

This looks like a temporary container used to restore a seek backup. The "galland_cason" name will just be a random name generated by Docker for the container, if a name hasn't been explicitly supplied.

It seems to match the steps described to backup and restore from the SEEK Documentation at https://docs.seek4science.org/tech/docker/docker-compose.html (under Backup and Restore).


Have you, or another administrator, been experimenting with doing backups and restore? There is nothing within the SEEK docker-compose itself that would trigger these steps.

regards,

Stuart.

--
You received this message because you are subscribed to the Google Groups "SEEK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to seek-develope...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Maria Sorokina

unread,
Mar 14, 2019, 10:48:40 AM3/14/19
to SEEK Developers
Thank you for your reply, Stuart!
It can indeed be a temporary container, but nobody played with the backups, and I am the only administrator (of the server AND of the SEEK instance). I didn't even get the time to update to the version 1.8 yet, so nobody touched to the system for the last two months.
Wired!
Reply all
Reply to author
Forward
0 new messages