Co-founder and software engineer at http://portainer.io
Nothing here yet.
No blogs yet.
I guess that it really depends on what you need to achieve and how complex your Wordpress setup is? If you plan to do some local development, then I'd +1 Docker (with Docker-compose) as well as it will make things go quicker. You can have a look at the following stack: https://github.com/wodby/docker4wordpress As well as this video tutorial: https://www.youtube.com/watch?v=d-S08uWq7r8
As Dong Nguyen stated, you'll probably need a reverse-proxy to map your API container to the myapp.com/api location. I'd recommend using Nginx, have a look at Frank Rousseau 's answer below for an example with Nginx. In addition to that, I wanted to recommend you a few things: You should stop using the --link option Using the --link option to link container is deprecated since Docker 1.9 and will probably be removed in future versions: https://docs.docker.com/engine/userguide/networking/default_network/dockerlinks/ What you should do instead is to create your own Docker network and start your containers inside that network. Containers started inside a user-defined network will be able to communicate by using their container names. Here is a small example: $ docker network create myapp $ docker run - d - p 27017 : 27017 --name mongodb mongo $ docker run - d - p 3000 : 3000 --name backend myapp/backend $ docker run - d - p 80 : 80 --name frontend myapp/frontend Give a try to docker-compose Compose is tool for defining and running multi-container Docker application. You'll be able to define what services (mongodb, backend, frontend) that make up your app in a single YAML file and manage it using a single command-line. It's pretty handy ! Have a look here for more information: https://docs.docker.com/compose/overview/
You could have a look at the logs first... It might help you figure out what's the problem: docker logs backend You can try to use the following Dockerfile: FROM keymetrics/pm2-docker-alpine RUN npm install pm2 -g WORKDIR /pm COPY . /pm/ CMD [ "pm2-docker" , "ecosystem.config.js" ] The WORKDIR instruction will create a new /pm folder in the container and set this folder as the working directory for the next COPY and CMD commands, see: https://docs.docker.com/engine/reference/builder/#workdir In the CMD instruction, there is no need to specify the path to the ecosystem.config.js file as it should be copied in the /pm directory which is the working directory. Give it a try.
Each time you use docker run (using the same image or not), you're actually creating and starting a new instance of a Docker image. A Docker image is a list of layers representing file system differences. It is used by Docker to create the base file system of your containers (these layers are read-only , allowing Docker to re-use them when you start multiple containers, making docker run really fast as well as not taking too much disk space). Basically, when you start a container, Docker will use the layers of the image to create the file system of your container. As I told you before, it's using read-only layers from the image, so in order to store any change in the container, Docker will add an extra read-write layer on top of that when the container is started. Every change you're making to a container is stored in this new read-write layer. If you delete the container, that layer will be deleted too, making the container non-persistent. I recommend having a look at this section of the documentation: https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/#container-and-layers
It's not an orchestrator, it's a management interface built on top of the Docker API. It'll help you manage all your Docker resources (containers, volumes, images, networks) as well as your Docker clusters (it supports Swarm and hence allow you to manage your Docker services). Give it a try, or have a look at our public demo (link is on the website).
I recommend to explore the official documentation first as Siddarthan Sarumathi Pandian told. After that, you might want to give a try to Portainer.io. It's an administration UI for Docker designed to simplify Docker usage. Disclaimer: I work for Portainer.io
Nice, note that you can use the following one-liners too: # Remove all dangling images (unused images) $ docker rmi $(sudo docker images -q -f "dangling=true" ) # Remove all dangling volumes (unused volumes) $ docker volume rm $(docker volume ls -q -f "dangling=true" )
Hey Marte ! Sorry for the late answer, it looks like you're using Docker for Windows (and not Docker on Windows, as usual Docker as issues with naming and it become confusing). Docker for Windows is actually Docker running inside a VM on Linux whereas Docker on Windows is the Docker engine running on Windows... So, just pull portainer/portainer :-) See this issue for more details: https://github.com/portainer/portainer/issues/328