Canadian software engineer living in Europe.

  • 5 Posts
  • 121 Comments
Joined 2 years ago
cake
Cake day: June 7th, 2023

help-circle

  • You can’t really make them go idle, save by restarting them with a do-nothing command like tail -f /dev/null. What you probably want to do is scale a service down to 0. This leaves the declaration that you want to have an image deployed as a container, “but for right now, don’t stand any containers up”.

    If you’re running a Kubernetes cluster, then this is pretty straightforward: just edit the deployment config for the service in question to set scale: 0. If you’re using Docker Compose, I believe the value to set is called replicas and the default is 1.

    As for a limit to the number of running containers, I don’t think it exists unless you’re running an orchestrator like AWS EKS that sets an artificial limit of… 15 per node? I think? Generally you’re limited only by the resources availabale, which means it’s a good idea to make sure that you’re setting limits on the amount of RAM/CPU a container can use.







  • Daniel Quinn@lemmy.catoLinux@lemmy.mlDo you use Gnome or KDE Plasma?
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    3
    ·
    15 days ago

    I used KDE for about 10 years, but switched to GNOME when 3 came out and haven’t looked back. It’s a little unusual if you’re coming from Windows, but I’ve found that once I let go of old paradigms like a start bar and icons and embraced multiple workspaces, that GNOME is pretty damned amazing.