perhaps a little off topic but... one postgres per app database or one shared postgres container with multiple app databases?
shared container pros: easier to manage, backup, replicate. Cons: single point of failure (all apps down if pg container goes down)
per app postgres pros - resilience/app isolation; Cons: different versions, more stuff to maintain, replicate
How do you decide?
I am currently using 1.9-aeee736 - and i have a problem viewing logs. The page is getting an typeError ...
main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:163 TypeError: Cannot read property 'charAt' of null
at E (main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:361)
at Td (main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:128)
at mg (main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:136)
at hi (main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:152)
at Qg (main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:190)
at Rg (main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:191)
at Sc (main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:204)
at Z (main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:202)
at Zg (main.js?r=aeee736a2f8cbdfd45049b298ea6b507a0c50021:205)
I am running in docker with latest tag.
docker stack rm swarmpit
... services: agent: image: swarmpit/agent:latest volumes: - /var/run/docker.sock:/var/run/docker.sock:ro logging: options: max-size: 5M deploy: mode: global resources: limits: cpus: '0.10' memory: 64M reservations: cpus: '0.05' memory: 32M
Are there any memory/resource leak issues known for AWS ECR registry support and/or autoredeploy? It might be a coincidence, but since I added a service in a private AWS ECR registry with autoredeploy I've had memory issues with the swarmpit container. I've just restarted the swarmpit container today (actually, had to restart manager node as it also used up all system threads, so I couldn't ssh in) and am monitoring for a few hours and then will be turning off the autoredeploy; but was just curious if others had seen this?