Support for the version 2 compose file format was introduced in docker-compose [version 1.6](https://blog.docker.com/2016/02/compose-1-6/), released around February of this year.

You&#39;re using 1.3.3, from July 2015.

You need to upgrade to a more recent version to use the version 2 format configuration files.

Since this is the first result on Googling &quot;docker-compose Unsupported config option for services&quot;, I would like to add that the most common reason as of 2020 is missing of `version: &quot;3&quot;`.

Just add `version: &quot;3&quot;` to the start of your `docker-compose.yml`.

From the [docs](https://docs.docker.com/compose/compose-file/compose-versioning/):

&gt; There are currently three versions of the Compose file format:
&gt; 1. Version 1, the legacy format. This is specified by omitting a version key at the root of the YAML.
&gt; 2. Version 2.x. This is specified with a version: &#39;2&#39; or version: &#39;2.1&#39;, etc., entry at the root of the YAML.
&gt; 3. Version 3.x, the latest and recommended version, designed to be cross-compatible between Compose and the Docker Engine’s swarm mode. This is specified with a version: &#39;3&#39; or version: &#39;3.1&#39;, etc., entry at the root of the YAML.

In my case i had used a wrong indentation. Recheck indentation of your ```docker-compose``` file to ensure it is correct

The EC2 instance/live web can connect just fine to the RDS database. But when I want to debug the code in my local machine, I can&#39;t connect to the database and got this error:

&gt; OperationalError: (2003, &quot;Can&#39;t connect to MySQL server on &#39;aa9jliuygesv4w.c03i1
ck3o0us.us-east-1.rds.amazonaws.com&#39; (10060)&quot;)

I&#39;ve added `.pem` and `.ppk` keys to `.ssh` and I already configure EB CLI. I don&#39;t know what should I do anymore.

FYI: The app is in Django

AWS: can&#39;t connect to RDS database from my machine

Last week I was working on a Java EE project with IntelliJ IDE.

Today: As I started up my IntelliJ 2016.1 and it gave me the error:

**Error Loading Project**

*Cannot load module FirstWebApp*

As I looked at the details it said it could not find my FirstWebApp.iml file and so could not load my project. 

I checked out my project structure in the Explorer and everything except the iml file were there. I also looked at the Recycle Bin but I couldn&#39;t find it there as well.

 - How can such a file just disappear?
   
 - How can I get my iml file back if its possible? 
   
 - What do these iml files do?

I&#39;m new in the Java World. If more information is needed just comment! :)

IntelliJ IDE | .iml File lost or deleted

I am going through the [_Getting Started with Docker Compose_](https://docs.docker.com/compose/gettingstarted/) page.

In Step 3, I made a `docker-compose.yml` file as described:

    version: &#39;2&#39;
    services:
        web:
            build: .
            ports: 
                - &quot;5000:5000&quot;
            volumes: 
                - .:/code
            depends_on:
                - redis
        redis:
            image: redis

But when I run: 

    $ docker-compose up

I get following error:

&gt; Unsupported config option for services service: &#39;web&#39;

What am I doing wrong? I was not able to figure out what is going on.

docker-compose : Unsupported config option for services service: &#39;web&#39;

I am going through the <a href="https://docs.docker.com/compose/gettingstarted/" target="_blank" rel="noopener noreferrer">Getting Started with Docker Compose</a> page.
In Step 3, I made a <code>docker-compose.yml</code> file as described:
<pre><code class="hljs language-yaml">version: '2'
services:
 web:
 build: .
 ports: 
 - "5000:5000"
 volumes: 
 - .:/code
 depends_on:
 - redis
 redis:
 image: redis
</code></pre>
But when I run:
<pre><code class="hljs language-ruby">$ docker-compose up
</code></pre>
I get following error:
> Unsupported config option for services service: 'web'
What am I doing wrong? I was not able to figure out what is going on.

On *nix systems, it is possible to bind-mount the docker socket from the host machine to the VM by doing something like this:

`docker run -v /var/run/docker.sock:/var/run/docker.sock ...`

Is there an equivalent way to do this when running docker on a windows host?

----------

I tried various combinations like:

`docker run -v tcp://127.0.0.1:2376:/var/run/docker.sock ...`

`docker run -v &quot;tcp://127.0.0.1:2376&quot;:/var/run/docker.sock ...`

`docker run -v localhost:2376:/var/run/docker.sock ...`

none of these have worked.

Bind to docker socket on Windows

**Docker** kind of always had a `USER` command to run a process as a specific user, but in general a lot of things had to run as ROOT.

I have seen a lot of images that use an `ENTRYPOINT` with `gosu` to de-elevate the process to run.

I&#39;m still a bit confused about the need for `gosu`. Shouldn&#39;t USER be enough? 

I know quite a bit has changed in terms of security with Docker 1.10, but I&#39;m still not clear about the recommended way to run a process in a docker container. 

Can someone explain when I would use `gosu` vs. `USER`? 

Thanks


EDIT:

The Docker [best practice guide][1] is not very clear: It says if the process can run without priviledges, use `USER`, if you need sudo, you might want to use `gosu`. 
That is confusing because one can install all sorts of things as ROOT in the `Dockerfile`, then create a user and give it proper privileges, then finally switch to that user and run the `CMD` as that user.
So why would we need sudo or `gosu` then?


  [1]: https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/

Docker using gosu vs USER

I&#39;m new to Docker and trying to make a demo Rails app. I made a dockerfile that looks like this: 

    FROM ruby:2.2
    MAINTAINER marko@codeship.com
    
    # Install apt based dependencies required to run Rails as 
    # well as RubyGems. As the Ruby image itself is based on a 
    # Debian image, we use apt-get to install those.
    RUN apt-get update &amp;&amp; apt-get install -y \
    build-essential \
    nodejs
    
        # Configure the main working directory. This is the base 
        # directory used in any further RUN, COPY, and ENTRYPOINT 
        # commands.
    RUN mkdir -p /app
    WORKDIR /app
    
        # Copy the Gemfile as well as the Gemfile.lock and install 
        # the RubyGems. This is a separate step so the dependencies 
        # will be cached unless changes to one of those two files 
        # are made.
    COPY Gemfile Gemfile.lock ./
    RUN gem install bundler &amp;&amp; bundle install --jobs 20 --retry 5
    
    # Copy the main application.
    COPY . ./
    
    # Expose port 8080 to the Docker host, so we can access it 
    # from the outside.
    EXPOSE 8080
    
    # The main command to run when the container starts. Also 
    # tell the Rails dev server to bind to all interfaces by 
    # default.
    CMD [&quot;bundle&quot;, &quot;exec&quot;, &quot;rails&quot;, &quot;server&quot;, &quot;-b&quot;, &quot;0.0.0.0&quot;, &quot;-p&quot;, &quot;8080&quot;]

I then built it like so: 

    docker build -t demo . 

And call a command to start the server which does start the server on port 8080: 

    Johns-MacBook-Pro:demo johnkealy$ docker run -it demo
    =&gt; Booting WEBrick
    =&gt; Rails 4.2.5 application starting in development on http://0.0.0.0:8080
    =&gt; Run `rails server -h` for more startup options
    =&gt; Ctrl-C to shutdown server
    [2016-04-23 16:50:34] INFO  WEBrick 1.3.1
    [2016-04-23 16:50:34] INFO  ruby 2.2.4 (2015-12-16) [x86_64-linux]
    [2016-04-23 16:50:34] INFO  WEBrick::HTTPServer#start: pid=1 port=8080

I then try to find the correct IP to navigate to: 

    Johns-MacBook-Pro:demo johnkealy$ docker-machine ip default
    192.168.99.100

I navigate to http://192.168.99.100:8080 and get the error This site can’t be reached 192.168.99.100 refused to connect.

What could I be doing wrong ? 




Connection refused on docker container

I am using kubernetes on a single machine for testing, I have built a custom image from the nginx docker image, but when I try to use the image in kubernetes I get an image pull error?????


**MY POD YAML**

&lt;!-- begin snippet: js hide: false --&gt;

&lt;!-- language: lang-none --&gt;

    kind: Pod
    apiVersion: v1
    metadata:
      name: yumserver
      labels:
        name: frontendhttp
    spec:
      containers:
        - name: myfrontend
          image: my/nginx:latest
          ports:
            - containerPort: 80
              name: &quot;http-server&quot;
          volumeMounts:
          - mountPath: &quot;/usr/share/nginx/html&quot;
            name: mypd
      imagePullSecrets:
        - name: myregistrykey

      volumes:
        - name: mypd
          persistentVolumeClaim:
           claimName: myclaim-1

&lt;!-- end snippet --&gt;


**MY KUBERNETES COMMAND**

kubectl create -f pod-yumserver.yaml



**THE ERROR**

&lt;!-- begin snippet: js hide: false --&gt;

&lt;!-- language: lang-none --&gt;

    kubectl describe pod yumserver


    Name: yumserver
    Namespace: default
    Image(s):	my/nginx:latest
    Node:		127.0.0.1/127.0.0.1
    Start Time:	Tue, 26 Apr 2016 16:31:42 +0100
    Labels:		name=frontendhttp
    Status:		Pending
    Reason:		
    Message:	
    IP:		172.17.0.2
    Controllers:	&lt;none&gt;
    Containers:
      myfrontend:
        Container ID:	
        Image:		my/nginx:latest
        Image ID:		
        QoS Tier:
          memory:		BestEffort
          cpu:		BestEffort
        State:		Waiting
          Reason:		ErrImagePull
        Ready:		False
        Restart Count:	0
        Environment Variables:
    Conditions:
      Type		Status
      Ready 	False 
    Volumes:
      mypd:
        Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
        ClaimName:	myclaim-1
        ReadOnly:	false
      default-token-64w08:
        Type:	Secret (a secret that should populate this volume)
        SecretName:	default-token-64w08
    Events:
      FirstSeen	LastSeen	Count	From			SubobjectPath			Type		Reason			Message
      ---------	--------	-----	----			-------------			--------	------			-------
      13s		13s		1	{default-scheduler }					Normal		Scheduled		Successfully assigned yumserver to 127.0.0.1
      13s		13s		1	{kubelet 127.0.0.1}					Warning		MissingClusterDNS	kubelet does not have ClusterDNS IP configured and cannot create Pod using &quot;ClusterFirst&quot; policy. Falling back to DNSDefault policy.
      12s		12s		1	{kubelet 127.0.0.1}	spec.containers{myfrontend}	Normal		Pulling			pulling image &quot;my/nginx:latest&quot;
      8s		8s		1	{kubelet 127.0.0.1}	spec.containers{myfrontend}	Warning		Failed			Failed to pull image &quot;my/nginx:latest&quot;: Error: image my/nginx:latest not found
      8s		8s		1	{kubelet 127.0.0.1}					Warning		FailedSync		Error syncing pod, skipping: failed to &quot;StartContainer&quot; for &quot;myfrontend&quot; with ErrImagePull: &quot;Error: image my/nginx:latest not found&quot;

&lt;!-- end snippet --&gt;






kubernetes cannot pull local image

There are scope of services which defined in docker-compose.yml. These service have been started. I need to rebuild only one of these and start it without up other services.
I run the following commands:

    docker-compose up -d # run all services
    docker-compose stop nginx # stop only one. but it still running !!!
    docker-compose build --no-cache nginx 
    docker-compose up -d --no-deps # link nginx to other services

At the end i got old nginx container.
By the way docker-compose doesn&#39;t kill all running containers !

How to rebuild docker container in docker-compose.yml?

I am trying to run the latest stable version of docker and docker-compose.

I am following the instructions on https://docs.docker.com/engine/installation/linux/ubuntulinux/

Apparently the current version of docker-compose is 1.7. 

Yet, after running through the documentation, installing docker-engine, I then get:

    $ docker-compose --version
    docker-compose version: 1.4.0

And

    $ docker --version
    Docker version 1.11.1, build 5604cbe



When I try to update it, I get the following:

    $ sudo apt-get upgrade docker-engine
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    Calculating upgrade... docker-engine is already the newest version.
    Done

**Update**

This just keeps getting stranger. After trying all of the advice below, I now get this:

    $ docker-compose -v
    The program &#39;docker-compose&#39; is currently not installed. You can install it by typing:
    sudo apt-get install docker-compose
    anton@Charles:~$ sudo apt-get install docker-compose
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    docker-compose is already the newest version.
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



How then can I update docker?





Ubuntu and updating Docker

I would like to use the psql in the postgres image in order to run some queries on the database.
But unfortunately when I attach to the postgres container, I got that error the psql command is not found...

For me a little bit it is a mystery how I can run postgre sql queries or commands in the container.

How run the psql command in the postgres container? (I am a new guy in Docker world)

I use Ubuntu as a host machine, and I did not install the postgres on the host machine, I use the postgres container instead.

&lt;!-- language: lang-none --&gt;

    docker-compose ps
            Name                       Command               State               Ports            
    ---------------------------------------------------------------------------------------------
    yiialkalmi_app_1        /bin/bash                        Exit 0                               
    yiialkalmi_nginx_1      nginx -g daemon off;             Up       443/tcp, 0.0.0.0:80-&gt;80/tcp 
    yiialkalmi_php_1        php-fpm                          Up       9000/tcp                    
    yiialkalmi_postgres_1   /docker-entrypoint.sh postgres   Up       5432/tcp                    
    yiialkalmi_redis_1      docker-entrypoint.sh redis ...   Up       6379/tcp     

Here the containers:

&lt;!-- language: lang-none --&gt;

    docker ps
    CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                         NAMES
    315567db2dff        yiialkalmi_nginx    &quot;nginx -g &#39;daemon off&quot;   18 hours ago        Up 3 hours          0.0.0.0:80-&gt;80/tcp, 443/tcp   yiialkalmi_nginx_1
    53577722df71        yiialkalmi_php      &quot;php-fpm&quot;                18 hours ago        Up 3 hours          9000/tcp                      yiialkalmi_php_1
    40e39bd0329a        postgres:latest     &quot;/docker-entrypoint.s&quot;   18 hours ago        Up 3 hours          5432/tcp                      yiialkalmi_postgres_1
    5cc47477b72d        redis:latest        &quot;docker-entrypoint.sh&quot;   19 hours ago        Up 3 hours          6379/tcp                      yiialkalmi_redis_1

And this is my docker-compose.yml:

&lt;!-- language: lang-none --&gt;

    app:
    image: ubuntu:16.04
    volumes:
        - .:/var/www/html

    nginx:
        build: ./docker/nginx/
        ports:
            - 80:80
        links:
            - php
        volumes_from:
            - app
        volumes:
            - ./docker/nginx/conf.d:/etc/nginx/conf.d
    
    php:
        build: ./docker/php/
        expose:
            - 9000
        links:
            - postgres
            - redis
        volumes_from:
            - app
    
    postgres:
        image: postgres:latest
        volumes:
            - /var/lib/postgres
        environment:
            POSTGRES_DB: project
            POSTGRES_USER: project
            POSTGRES_PASSWORD: project
    
    redis:
        image: redis:latest
        expose:
            - 6379

Docker - How can run the psql command in the postgres container?

THIS IS A SAMPLE QUESTION! NEVER DO IT IN PRODUCTION. RUN NGINX / PHP / OTHER SERVICES IN SEPARATE CONTAINERS!

When I start `docker-compose up` the Ubuntu container exits with `ubuntu exited with code 0`.

When I run `docker run -d -ti -p 80:80 -v ~/sph/laravel52:/www/laravel ubuntu`, all works fine. 

How can I replicate this behavior using Docker Compose?

This is my `Dockerfile`:

    # Version: 0.0.1
    FROM ubuntu:15.04
    
        
    
    ENV DEBIAN_FRONTEND noninteractive
    
    #INSTALL ALL
    RUN apt-get update &amp;&amp; apt-get install -y  \
           nano \
           php5-fpm \
           php5-mysql \
           nginx
    
    
    
    #NGINX CONF
    ADD nginx/sites-available/laravel.conf /etc/nginx/sites-available/
    RUN rm /etc/nginx/sites-available/default
    RUN mv /etc/nginx/sites-available/laravel.conf /etc/nginx/sites-available/default
    
    VOLUME /www
    
    
    ENTRYPOINT nginx &amp;&amp; service php5-fpm start &amp;&amp; /bin/bash
    
    CMD [&quot;true&quot;]
    
    
    EXPOSE 80

And `docker-compose.yml`:

    version: &#39;2&#39;
    services:
      ubuntu:
            build: .
            container_name: ubuntu
            volumes:
                - ~/sph/laravel52:/www/laravel
            ports:
              - &quot;80:80&quot;

Docker-Compose with multiple services

When I use `docker-compose up` I can see logs for all containers in my `docker-compose.yml` file.

However, when I use `docker-compose run app` I only see console output for `app` but none of the services that `app` depends on. How can see log output for the other services?

Content Type	Original Author	Original Content on Stackoverflow
Question	DarcliGht	View Question on Stackoverflow
Solution 1 - Docker	larsks	View Answer on Stackoverflow
Solution 2 - Docker	ospider	View Answer on Stackoverflow
Solution 3 - Docker	Muteshi	View Answer on Stackoverflow

docker-compose : Unsupported config option for services service: 'web'

Docker Problem Overview

Docker Solutions

Solution 1 - Docker

Solution 2 - Docker

Solution 3 - Docker

IntelliJ IDE | .iml File lost or deleted

AWS: can't connect to RDS database from my machine

Attributions