Hot answers tagged

2

AWS container service team member here. IF you are still early on in your journey to automate this via a CLI I would suggest you consider moving past the ecs-cli. The follow-on version of this CLI is called AWS Copilot and has more sophistication to implement those workflows. Note that Copilot dropped support for docker compose because we have implemented a ...


2

This isn't really an ArgoCD thing. Keel is a good tool to help keep your images updated across the cluster and is super easy to implement. Basically, you'd just add some annotations to your manifest. metadata: annotations: keel.sh/policy: force keel.sh/trigger: poll keel.sh/pollSchedule: "@every 10m" It may be worth noting that ...


1

What you are looking for is a sidecar pattern where you run a container of your main application and a number of additional containers (one or more) in support of it. This is a well established pattern with orchestrators such as ECS but it's not possible to declare it with a docker compose syntax today. There is an open request talking about this. Can I ask ...


1

yarn start should be the CMD of your docker image (I.e what is run when you start a container) and not a RUN command (which is run when creating the image used to satrt a container later) From your exemple, something like this should be better: FROM node:12-alpine WORKDIR /app COPY ./server /app WORKDIR /app/server RUN yarn CMD yarn start


1

Your next step will be to identify a solution for container orchestration. For a quick dev test solution, you could host your own docker registry, push your built image to the registry, and add a deployment step that stops the existing container and spins up a new one from your registry. However, in a production setting there are many other aspects to ...


1

It's a pretty general question, I will try to answer the best I can: If you want to just build and run an image: Build the project: npx expo-cli init react_native_app --npm You need to create a Dockerfile file in your repository Docker build -t {tag_name} . (You can replace '.' eith the Dockerfile path) Docker run... If you want you can create docker ...


1

I recently had this frustrating problem but I managed to fix it today. What I did, is in the desktop app on Windows / Mac you can edit the Daemon file. Under Settings in the Docker App under Docker Engine, I added the line at the bottom of the file just above the last curly brace. "dns": [ "192.168.4.100", "8.8.8.8" ] This then ...


Only top voted, non community-wiki answers of a minimum length are eligible