Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support docker-compose version 3

See original GitHub issue

Description

I have a docker-compose file in version 3, but when i add it as an external compose file to run, it falis saying only version 2.x is supported. EXAMPLE

<plugin>
                <inherited>false</inherited>
                <groupId>io.fabric8</groupId>
                <artifactId>docker-maven-plugin</artifactId>
                <version>0.25.2</version>
                <extensions>true</extensions>
                <configuration>
                    <images>
                        <image>
                            <name>sample-project:latest</name>
                            <build>
                                <dockerFileDir>${project.basedir}</dockerFileDir>
                                <dockerFile>docker/Dockerfile</dockerFile>
                                <assembly>
                                    <mode>dir</mode>
                                    <descriptorRef>artifact</descriptorRef>
                                </assembly>
                            </build>
                        </image>
                        <image>
                            <alias>sample-project-stack</alias>
                            <name>sample-project:latest</name>
                            <external>
                                <type>compose</type>
                                <basedir>${project.basedir}</basedir>
                                <composeFile>docker/docker-compose.yml</composeFile>
                            </external>
                            <run>
                                <namingStrategy>alias</namingStrategy>
                            </run>
                        </image>
                    </images>
                </configuration>
            </plugin>

Info

d-m-p version : 0.25.2
Maven version (mvn -v) :

❯ mvn -v
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T11:49:05-08:00)
Maven home: /Users/hshah/Applications/apache-maven-3.5.3
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_151.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"

Docker version :

 docker -v
Docker version 17.09.0-ce, build afdb6d4

Issue Analytics

State:
Created 5 years ago
Reactions:11
Comments:6

Top GitHub Comments

4reactions

rhusscommented, Apr 16, 2019

I don’t plan to actively work on that. 'happy to help in integrating a PR request for this upgrade though.

However, long-term docker:run will be feature-frozen as I would recommend testcontainers.org as the better alternative for integration tests. That way we can focus better on creating images with other technologies like Jib or other daemonless builder tools like Buildah. This is not written in stone, however its probably the direction where d-m-p is heading to.

0reactions

guccecommented, Feb 8, 2021

@rhuss Thanks Roland. Works like charm! I was gonna complain about the missing functionality but now I try testcontainers. Greetings from Munich.