How LeetCode Prevents Your Code from Crashing Their Servers
Explore the engineering behind LeetCode's judge system, from container isolation and cgroups to the challenges of multi-language resource calibration.
Loading…
ReadMeFeed / Community knowledge
#containers
Real questions. Useful conversations. Find the people who know your stack.
leetcode
Taming Memory Spikes with Linux cgroups v2: Beyond the Hard Limit
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.
Azure Container Registry: pull a pinned image with the workload's managed identity
Grant Azure Container Registry pull access with the correct role mode, select the workload identity, and verify an immutable image without shared registry passwords.
Azure Container Apps revisions: validate a release before moving traffic
Use Azure Container Apps revision modes, readiness checks and traffic weights to test a candidate release and verify the behavior of the active version.
How to use ss in specific network namespace
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
How to run amd64 docker image on arm64 host platform?
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
docker
Expose Both Ports 8080 and 3000 For Cloud Run Deployment
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
NodeJS 14.x - Native AWS Lambda Import/Export Support
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
Limits of Docker container time zone configuration across base images
Docker Engine does not offer a daemon-level default time zone for containers, leaving each container's local time dependent on image contents, environment variables, and bind mounts. Setting TZ via docker run -e is the documented way to configure a named zone, but its behavior is bounded by the image's userspace libraries and time zone database. In glibc-bas