Available Docker images

Below is the list of all avaialble Docker images in public Registry. The images can be used to run Extender in environment with old SDKs that are no longer supported.

How to use old Docker images

To use old environment you should go through following steps:

1. Modify docker-compose.yml from Extender’s repository link. Need to add one more definition of service with necessary Docker image. For example, if we want to use Docker image that contains Emscripten 2.0.11 we need to add following service definition:

    emscripten_2011-dev:
        image: europe-west1-docker.pkg.dev/extender-426409/extender-public-registry/extender-emsdk-2011-env:latest
        extends:
        file: common-services.yml
        service: remote_builder
        profiles:
        - all
        - web
        networks:
        default:
            aliases:
            - emsdk-2011
   

   Important fields are:

   • profiles - list of profiles that triggers service start. Profile names passed via --profile <profile_name> argument to docker compose command.
   • networks - list of networks that should used by Docker container. For running Extender used network with name default. Important to set service network aliases (it will be used in later Extender’s configuration).
2. Add definition of remote builder in application-local-dev-app.yml in extender.remote-builder.platforms section. In our example it will looks like:

        emsdk-2011:
            url: http://emsdk-2011:9000
            instanceId: emsdk-2011
   

   Url should be in following format: http://<service_network_alias>:9000, where service_network_alias - network alias from step 1. 9000 - standard port for Extender (can be different if you are using custom Extender configuration).

3. Run local Extender as it described in How to run local Extender with preconfigured artifacts.