Hello fellow Sprykers, I have a general questions concerning the docker/sdk and if it is possible to directly tag images in a gitlab-pipeline via docker/sdk for a later push to registry (in my case the gitlab image registry). I kinda got it working via a "hack" until a certain point: Using namespace and tag in the deploy.yml like this it generates images with tags which are directly push-able.

version: "0.1"

namespace: "<http://registry.gitlab.com/mycorp/project/image|registry.gitlab.com/mycorp/project/image>"
tag: ${CI_COMMIT_SHA}

environment: docker
pipeline: docker
image:
    tag: spryker/php:7.4-alpine3.13
...

docker/sdk log says:

exporting layers
exporting layers 0.1s done
writing image sha256:7adec4f7745a08c03202dfe92e501e3f01b5acc3cc595b92c831099f16538348 done
naming to <http://registry.gitlab.com/mycorp/project/image_gateway:e0e8fd49464ff220c85dac9606b0f829d92b9eca|registry.gitlab.com/mycorp/project/image_gateway:e0e8fd49464ff220c85dac9606b0f829d92b9eca> done
...

I just have to push these images with all their tags now. After a

docker/sdk boot deploy.yml

I'm able to pull these images e.g. in another stage (for codeception tests) of the pipeline, BUT when I try to

docker/sdk up

this environment, it fails to check if the database-service runs. This is because the container-names are missing the slashes and dots from the namespace. The check in docker/deployment/default/bin/sdk/runtime/wait.sh expects the container to be named:

<http://registry.gitlab.com/mycorp/project/image_database_*|registry.gitlab.com/mycorp/project/image_database_*>

but it is

registrygitlabcommycorpprojectimage_database_*

Question: Is there anyway to get around these limitations? Are there better ways to tag, pull and boot the images with docker/sdk? Or is there anything on the roadmap?