Problems with "platform"

[Bronson-Brown-deVost]

I have several images that are only built for the linux/amd64 platform. With "container run" I can use these with the "--arch amd64" command line argument. With "container-compose" I am unsure how to use that option, my compose files keep failing with Error: unsupported: "platform linux/arm64", which is the error I get with "container run" if I do not have the "--arch amd64" command line argument.

I believe docker compose v2.4 had a "platform" option, but I think this has been removed with v3. Is there any way to use "--arch amd64" with container-compose?

[Mcrich23]

Unless something went wrong in the migration to the ContainerCommands library, Compose should respect a platform if you specify it.

[Bronson-Brown-deVost]

Thank you for responding so quickly!

Here is my docker-compose.yml:

# This is a docker-compose file for developing SQE_API
# Start it up and you get all the services
version: '3.7'

services:
    sqe-database:
        image: qumranica/sqe-database:0.32.3
        platform: linux/amd64
        container_name: SQE_Database
        # These environment variables match the default db connection settings for the project.
        environment:
            MYSQL_ROOT_PASSWORD: none
            MYSQL_USER: sqe_user
            MYSQL_PASSWORD: mysecretpw
            MYSQL_DATABASE: SQE
        expose:
            - "3306"
        ports:
            - "3307:3306"
        networks:
            - sqe_api

networks:
    sqe_api:

When I run container-compose up -d (v0.5.1) I get the following output:

❯ container-compose up --debug
Info: Docker Compose file version parsed as: 3.7
Note: The 'version' field influences how a Docker Compose CLI interprets the file, but this custom 'container-compose' tool directly interprets the schema.
Info: No 'name' field found in docker-compose.yml. Using directory name as project name: dev
Stopping container: dev-sqe-database

--- Processing Networks ---
Creating network: sqe_api (Actual name: sqe_api)
Executing container network create: container network create
Network 'sqe_api' already exists
--- Networks Processed ---


--- Processing Services ---
["sqe-database"]
Pulling Image qumranica/sqe-database:0.32.3...
Info: Using explicit container_name: SQE_Database
Info: Service 'sqe-database' is configured to connect to networks: sqe_api ascertained from networks attribute in docker-compose.yml.
Note: This tool assumes custom networks are defined at the top-level 'networks' key or are pre-existing. This tool does not create implicit networks for services if not explicitly defined at the top-level.

Starting service: sqe-database
Starting sqe-database
----------------------------------------

sqe-database: Error: unsupported: "platform linux/arm64"

Error Domain=ContainerWait Code=1 "Timed out waiting for container 'dev-sqe-database' to be running." UserInfo={NSLocalizedDescription=Timed out waiting for container 'dev-sqe-database' to be running.}

The container does, however, work with container run --name SQE_Database --env MYSQL_ROOT_PASSWORD=none --env MYSQL_USER=sqe_user --env MYSQL_PASSWORD=mysecretpw --env MYSQL_DATABASE=SQE --arch amd64 --publish 3307:3306 --detach qumranica/sqe-database:0.32.3

[Mcrich23]

Thank you! I found the issue. It appears to be an issue with os versus arch within the platform delimiter. This changed silently with container and I had no idea. Working on a fix right now!

[Mcrich23]

Never mind, those are just granular options in addition to platform. Still investigating

[Mcrich23]

it appears that the issue was in how it runs the container. I will be releasing the fix in the next release.