Is your feature request related to a problem? Please describe. I have several applications with their own Dockerfile within one project and in order to build, launch and test them locally I'm using docker-compose.

It seems like a good idea to reuse docker-compose commands to build, test and push images to registry from CI, so I decided to use them in Jenkinsfile. Project has package.json file with current version which is incremented during CI build. This version is used as tag for docker images.

docker-compose.yaml:

version: '2'

services:
  app1:
    image: my-registry.com/app1
    build:
      context: ./app1
    // other fields
  app2:
    image: my-registry.com/app2
    build:
      context: ./app2
    // other fields
  app3:
    image: my-registry.com/app3
    build:
      context: ./app3
    // other fields

The current CI pipeline looks as follows:

1) Build images
docker-compose build // generates images with "latest" tag

2) Test images
docker-compose run --rm app1 <test command> // the same for app2 and app3

3) If tests passed, increment version and use it as the next docker tag
npm version <patch/minor/major>
newVersion = readJSON('package.json').version

4) Tag and push images
composeServices = readYaml('docker-compose.yaml').services // { app1: { image: my-registry.com/app1 }, ... }
image = composeServices.app1.image // the same for app2 and app3
docker tag <image> <image>:<newVersion>
docker push <image>:<newVersion>

This pipeline works but I have to read compose file to get image that will be used in "docker tag" and "docker push" commands.

Describe the solution you'd like I'd like to have a new command:

docker-compose tag <service> <tag>
// for my example
docker-compose tag app1 <version from updated package.json>

And I want "push" command to support tag postfix:

docker-compose push <service>:<tag>
// for my example
docker-compose push app1:<version from updated package.json>

Describe alternatives you've considered Using "docker tag" and "docker push" explicitly but for that I need to read images from docker-compose.yaml file

Aug 14 '20 14:08 Jokero

moved to Reopened awaiting QA template - Please move into To Test once added, thanks!

Feb 24 '25 17:02 brudnak

QA Testing

Root cause

N/A

What was fixed, or what changes have occurred

We're adding a new feature imperative-api-extension that will be off by default.

When turned on:

A new HTTPS server is started listening on port localhost:6666
This server should be reachable by Kubernetes either directly (when IMPERATIVE_API_DIRECT=true) or indirectly otherwise.
RemoteDialerProxy is deployed when IMPERATIVE_API_DIRECT is not set to true. This happens when Rancher is started either with the binary or with docker directly. When deploying Rancher with helm, then RemoteDialer is not deployed.
A APIService for ext.cattle.io should be deployed. (We're still deploying one even though we don't have any store.. It's fine..)

Areas or cases that should be tested

What areas could experience regressions?

Rancher startup sequence when the feature is on, both with or without IMPERATIVE_API_DIRECT=true. This is because we're adding new CustomResources to Kubernetes, which may or may not be available right away based (especially true if we're waiting for RDP to be deployed).

Steps

Feature is off

Test that Rancher doesn't listen on localhost:6666.
When IMPERATIVE_API_DIRECT is true, verify that RemoteDialerProxy is not deployed. (kubectl -n cattle-system get deployments api-extension returns not found)
kubectl get apiservice v1.ext.cattle.io returns not found in both cases
Still able to access https://<rancher url>/ext/apis (make sure you set a valid rancher token in Authorization: Bearer <token> header. This should give you a 200.

Feature is on

Test that Rancher listens on localhost:6666
When IMPERATIVE_API_DIRECT is not true:
- verify that the service api-extension in cattle-system points to the deployments api-extension in cattle-system
- verify that RemoteDialerProxy is deployed. (kubectl -n cattle-system get deployments api-extension returns something)
When IMPERATIVE_API_DIRECT is true:
- verify that the service api-extension in cattle-system points to Rancher
- verify that RemoteDialerProxy is not deployed. (kubectl -n cattle-system get deployments api-extension returns not found)
kubectl get apiservice v1.ext.cattle.io returns the following (note that "True" column is important and says that everything is working fine. This might take a few seconds to get a "True" column:

$ kubectl get apiservice v1.ext.cattle.io 
NAME               SERVICE                                  AVAILABLE   AGE
v1.ext.cattle.io   cattle-system/imperative-api-extension   True        137m

kubectl api-resources shows at least one CustomResource from the ext.cattle.io group:

$ kubectl api-resources | grep ext.cattle.io
useractivities                                            ext.cattle.io/v1                  false        UserActivity

kubectl explain <resource> works for these resources:

$ kubectl explain useractivities
GROUP:      ext.cattle.io
KIND:       UserActivity
VERSION:    v1
...

Feb 24 '25 21:02 tomleb

🧪 Test Environment... CLICK TO EXPAND! ⬅️

Component	Version / Type
Rancher version	v2.11.0-alpha12
Installation option	Helm (high availability)
If Helm Chart k8s cluster	v1.31.2
Cert Details	external tls `aws acm`
Docker version	20.10.7, build f0df350
Downstream cluster type	N/A
Downstream K8s version	N/A
Authentication providers enabled	local
Logged in user role	admin
Webhook version	rancher/rancher-webhook:v0.7.0-rc.9

🧪 Test Cases

#	Priority	Description & Link	PASS/FAIL
1	P0	(Feat. on) local listening :6666	✅ PASS
2	P0	(Feat. on) Docker install service points to api-extension	✅ PASS
3	P0	(Feat. on) Docker install RemoteDialerProxy deployed	✅ PASS
4	P0	(Feat. on) Helm install service points to rancher	✅ PASS
5	P0	(Feat. on) Helm Install RemoteDialerProxy not deployed	✅ PASS
6	P0	(Feat. on) apiservice v1.ext.cattle.io returns avail true	✅ PASS
7	P0	(Feat. on) kubectl api-resources shows at least one CustomResource	✅ PASS
8	P0	(Feat. on) kubectl explain works for these resources	✅ PASS
9	P0	(Feat. off) Local doesn't listen on :6666	✅ PASS
10	P0	(Feat. off) apiservice v1.ext.cattle.io returns not found	✅ PASS
11	P0	(Feat. off) Still able to access https:///ext/apis	✅ PASS
12	P0	(Regression Test) Steve filter	✅ PASS
13	P0	(Regression Test) Steve limit	✅ PASS
14	P0	(Regression Test) Steve sort	✅ PASS
15	P0	Upgrade	✅ PASS

🚨 15 test cases... CLICK TO EXPAND! (For table links to work) ⬅️

1 / (Feat. on) local listening :6666 Status: ✅ PASS

:small_red_triangle: back to top

Test 1 details... Click to expand

Test Steps for Validation

kubectl -n cattle-system debug rancher-5ffc648559-l474t -it --image=alpine:latest
apk add iproute2
ss -lntp

✅ Expected Outcome

Port listening on :6666

✅ Actual Outcome

Port listening on :6666

2 / (Feat. on) Docker install service points to api-extension Status: ✅ PASS

:small_red_triangle: back to top

Test 2 details... Click to expand

Test Steps for Validation

Run the following command
kubectl get service imperative-api-extension -n cattle-system -o yaml | grep -A 1 selector
Ensure that the selector points to api-extension

✅ Expected Outcome

Selector set to api-extension

✅ Actual Outcome

Selector was api-extension

kubectl get service imperative-api-extension -n cattle-system -o yaml | grep -A 1 selector
  selector:

3 / (Feat. on) Docker install RemoteDialerProxy deployed Status: ✅ PASS

:small_red_triangle: back to top

Test 3 details... Click to expand

Test Steps for Validation

Run the following command:
kubectl -n cattle-system get deployments api-extension

✅ Expected Outcome

Should return a deployment

✅ Actual Outcome

It does return a deployment

NAME            READY   UP-TO-DATE   AVAILABLE   AGE
api-extension   1/1     1            1           70s

4 / (Feat. on) Helm install service points to rancher Status: ✅ PASS

:small_red_triangle: back to top

Test 4 details... Click to expand

Test Steps for Validation

Run the following command
kubectl get service imperative-api-extension -n cattle-system -o yaml | grep -A 1 selector
Ensure that the selector points to rancher

✅ Expected Outcome

Selector set to Rancher

✅ Actual Outcome

Selector was rancher

% kubectl get service imperative-api-extension -n cattle-system -o yaml | grep -A 1 selector

  selector:
    app: rancher

5 / (Feat. on) Helm Install RemoteDialerProxy not deployed Status: ✅ PASS

:small_red_triangle: back to top

Test 5 details... Click to expand

Test Steps for Validation

Run the following command:
kubectl -n cattle-system get deployments api-extension
Should return not found

✅ Expected Outcome

Should return not found

✅ Actual Outcome

Deployment was not found as expected

6 / (Feat. on) apiservice v1.ext.cattle.io returns avail true Status: ✅ PASS

:small_red_triangle: back to top

Test 6 details... Click to expand

Test Steps for Validation

Run the following command
kubectl get apiservice v1.ext.cattle.io
Should return true for available

✅ Expected Outcome

Available column to be set as true

✅ Actual Outcome

Available was true

7 / (Feat. on) kubectl api-resources shows at least one CustomResource Status: ✅ PASS

:small_red_triangle: back to top

Test 7 details... Click to expand

Test Steps for Validation

Run this command
kubectl api-resources | grep ext.cattle.io
Should return one resource at least

✅ Expected Outcome

One resource at least to be returned

✅ Actual Outcome

andrewbrudnak@Andrews-MacBook-Pro Downloads % kubectl api-resources | grep ext.cattle.io
useractivities                                            ext.cattle.io/v1                  false        UserActivity

8 / (Feat. on) kubectl explain works for these resources Status: ✅ PASS

:small_red_triangle: back to top

Test 8 details... Click to expand

Test Steps for Validation

Run the following command
kubectl explain useractivities

✅ Expected Outcome

Should get user activities returned

✅ Actual Outcome

Got user activities returned

9 / (Feat. off) Local doesn't listen on :6666 Status: ✅ PASS

:small_red_triangle: back to top

Test 9 details... Click to expand

Test Steps for Validation

kubectl -n cattle-system debug rancher-5ffc648559-l474t -it --image=alpine:latest
apk add iproute2
ss -lntp

✅ Expected Outcome

No port listening on :6666

✅ Actual Outcome

No port listening on :666

10 / (Feat. off) apiservice v1.ext.cattle.io returns not found Status: ✅ PASS

:small_red_triangle: back to top

Test 10 details... Click to expand

Test Steps for Validation

Run the following command
kubectl get apiservice v1.ext.cattle.io
Should return true for available

✅ Expected Outcome

Error from server (NotFound): apiservices.apiregistration.k8s.io "v1.ext.cattle.io" not found

✅ Actual Outcome

Error from server (NotFound): apiservices.apiregistration.k8s.io "v1.ext.cattle.io" not found

11 / (Feat. off) Still able to access https:///ext/apis Status: ✅ PASS

:small_red_triangle: back to top

Test 11 details... Click to expand

Test Steps for Validation

Visit https://<rancher url>/ext/apis
200 returned

✅ Expected Outcome

200 returned

✅ Actual Outcome

200 returned

12 / (Regression Test) Steve filter Status: ✅ PASS

:small_red_triangle: back to top

Test 12 details... Click to expand

Test Steps for Validation

Automated check

✅ Expected Outcome

Passing

✅ Actual Outcome

Passing

13 / (Regression Test) Steve limit Status: ✅ PASS

:small_red_triangle: back to top

Test 13 details... Click to expand

Test Steps for Validation

Automated check

✅ Expected Outcome

Passing

✅ Actual Outcome

Passing

14 / (Regression Test) Steve sort Status: ✅ PASS

:small_red_triangle: back to top

Test 14 details... Click to expand

Test Steps for Validation

Automated check

✅ Expected Outcome

Passing

✅ Actual Outcome

Passing

15 / Upgrade Status: ✅ PASS

:small_red_triangle: back to top

Test 15 details... Click to expand

Test Steps for Validation

Upgrade rancher
Rerun all test cases

✅ Expected Outcome

All passing

✅ Actual Outcome

All passing

Mar 13 '25 10:03 brudnak

Add docker-compose tag <service> <tag> and allow to push a specific tag by using push command

QA Testing

Root cause

What was fixed, or what changes have occurred

Areas or cases that should be tested

What areas could experience regressions?

Steps

Feature is off

Feature is on

🧪 Test Cases

1 / (Feat. on) local listening :6666 Status: ✅ PASS

2 / (Feat. on) Docker install service points to api-extension Status: ✅ PASS

3 / (Feat. on) Docker install RemoteDialerProxy deployed Status: ✅ PASS

4 / (Feat. on) Helm install service points to rancher Status: ✅ PASS

5 / (Feat. on) Helm Install RemoteDialerProxy not deployed Status: ✅ PASS

6 / (Feat. on) apiservice v1.ext.cattle.io returns avail true Status: ✅ PASS

7 / (Feat. on) kubectl api-resources shows at least one CustomResource Status: ✅ PASS

8 / (Feat. on) kubectl explain works for these resources Status: ✅ PASS

9 / (Feat. off) Local doesn't listen on :6666 Status: ✅ PASS

10 / (Feat. off) apiservice v1.ext.cattle.io returns not found Status: ✅ PASS

11 / (Feat. off) Still able to access https:///ext/apis Status: ✅ PASS

12 / (Regression Test) Steve filter Status: ✅ PASS

13 / (Regression Test) Steve limit Status: ✅ PASS

14 / (Regression Test) Steve sort Status: ✅ PASS

15 / Upgrade Status: ✅ PASS