this post was submitted on 09 Jul 2023
16 points (94.4% liked)

Sysadmin

7664 readers
5 users here now

A community dedicated to the profession of IT Systems Administration

No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
!lemmy@lemmy.ml
!lemmyworld@lemmy.world
!lemmy_support@lemmy.ml
!support@lemmy.world

founded 1 year ago
MODERATORS
DarraignTheSane@lemmy.world
00Lemming@lemmy.world
L3s@lemmy.world
16
How to deal with docker containers? (sopuli.xyz)
submitted 1 year ago by bretti_kivi@sopuli.xyz to c/sysadmin@lemmy.world
15 comments fedilink hide all child comments
 

I have inherited some cloud hosted vms, with several services hosted in docker containers on these. Think we server and then DB, both hosted in separate containers. Several (overpriced) vms are involved. Would really like some pointers as to how I can get into these / edit them. Would really like to consolidate. I use proxmox at home and am comfortable in Linux but this is new to me. Any docs / tutorials would be super helpful. Still don't really understand why the design was done quite like this, so if you have insight on that, please let me know why you would do it this way. Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] bretti_kivi@sopuli.xyz 2 points 1 year ago (1 children)

built by someone who is no longer with the company and no longer available to provide insight.

[–] awderon@lemmy.world 4 points 1 year ago (1 children)

Docker inspect $container should return you most of the info for the container. You can also get a shell inside the container via docker exec -it $container sh. If you have a dockerfile for the container you can see how the container has been set up.

Additionally the shell history can also yield useful information on what has been done. Docker saves the logs of running containers in /var/lib/docker/containers

[–] bretti_kivi@sopuli.xyz 2 points 1 year ago

thanks, super-useful. I think I will bring up a couple of docker containers at home and check where and what they log, then try and extrapolate from that. I've managed to get into a couple of them with the -it command.