ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to handle data and state in Scalingo's container architecture to avoid data loss caused by ephemeral file systems and buildpack automation.
Explore the engineering behind LeetCode's judge system, from container isolation and cgroups to the challenges of multi-language resource calibration.
Stop relying solely on the OOM Killer. Learn how to use Linux cgroups v2 memory.low, memory.high, and memory.max to create a tiered resource strategy that throttles instead of crashes.
Whilst investigating some TCP network issues in containers I tried to use ss to peek into container network TCP stack. We are running Amazon Linux in AWS: # uname -a Linux 4.14.173-137.229.amzn2.x86_64 #1 SMP Wed Apr 1 18:06:08 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ss has the following cli switch for that: -N NSNAME, --net=NSNAME Switch to the specified ne
I have an m1 mac and I am trying to run a amd64 based docker image on my arm64 based host platform. However, when I try to do so (with docker run) I get the following error: WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested. When I try adding the tag --platf
TL:DR - I am trying to deploy my MERN stack application to GCP's Cloud Run. Struggling with what I believe is a port issue. My React application is in a client folder inside of my Node.js application. Here is my one Dockerfile to run both the front-end and back-end: FROM node:13.12.0-alpine WORKDIR /app COPY . ./ # Installing components for be connector RUN
I am looking to make use of the native import/export that comes with ES6. I am using Serverless Containers within AWS Lambda. I have my Dockerfile which looks like this: FROM public.ecr.aws/lambda/nodejs:14 COPY app ./ RUN npm install CMD [ "app.handler" ] I then have an app directory with my application code. The app.js code looks like this: import { succes
Is it possible to... run a container with podman which has an IP on the same subnet that the host is on is accessible from every other host on the subnet including the host itself ? I had partial success using both a macvlan and ipvlan drivers - I am able to run a container, give it an IP address, and this IP is then accessible from every other host on the n
I always used docker-compose on Ubuntu, in this environment containers are named with underscore: <project>_<service>_<replica> But now, I switched to Windows 10 (using Docker Desktop) and naming convention has changed: <project>-<service>-<replica> I don't know if this is OS dependent but it's a problem. My scripts are fa
scalingo
leetcode
docker
podman