Apigee Emulator and Cloud Code Extension Not Connecting

[Jordan_Hood]

Been encountering several issues today when attempting to work with the Apigee emulator through the Cloud Code extension in VS Code.

Yesterday we had everything working using:

• Apigee Emulator version 1.9.2

• Cloud Code extension version 2.20.0

However, this morning the Cloud Code extension is no longer detecting the running emulator.

A colleague is experiencing similar problems with the latest emulator version (1.15.2). The emulator process starts and runs as expected, but Cloud Code does not register or connect to it.

To troubleshoot, we cleaned and reinstalled the necessary extensions. We also found that we now need to enable the Gemini extension for the Apigee section to appear and sign in to the Cloud Code extension, neither of which has been required previously.

This behaviour is new to us, and at present it is preventing our team from working with Apigee locally.

[rabustamante]

Hi @Jordan_Hood ,

I hope that you are doing well, taking a look at the screenshots that you shared it does not seem like it should be the expected behaviour. You should be able to use cloud code without gemini code assist.

Looking at my own set up it seems that there is quite a few newer versions of cloud code.

You mentioned that you are using 2.20.0 it seems that we are currently on version 2.31.0 is there a reason why you are using an older version of the extension?

[Jordan_Hood]

Hi @rabustamante

I was using 2.20.0 as there was a issue affecting my dev workflow that I did raise and caused me some fustrations (Command not found `geminicodeassist.saveKeysClicked` · Issue #1139 · GoogleCloudPlatform/cloud-code-vscode · GitHub), but this looks to have been resovoled.

I did test the latest version of the Cloud code extension, and I’m still getting the Error: Could not find the newly created container failure.

[rabustamante]

Jordan,

Have you tried any other version of the emulator?

Was there any changes in the configuration whenever the issue started?

Also found this which my be helpful: Apigee Emulator v1.14.2 in VSCode Failed to deploy environment - #10 by Chris_Dupuy

[Jordan_Hood]

Hi Rabustamante

I’ve tried several versions of the emulator from 1.9.2 to 1.15.2

• 1.9.2
• 1.10.4
• 1.11.2
• 1.12.4
• 1.13.3
• 1.14.3
• 1.15.1
• 1.15.2

On all of these VScode/Cloud Code is failing to detect the running emulator.

Was there any changes in the configuration whenever the issue started?

Nope we’ve not made chages to our configuration.

As for that link you shared, It doesn’t help out, I’m using colima

colima version
colima version 0.9.1
git commit: 0cbf719f5409ce04b9f0607b681c005d2ff7d94a

runtime: docker
arch: aarch64
client: v29.0.2
server: v28.4.0

[Jordan_Hood]

Ok think I’ve narrowed the issue down to a mismatch between the Cloud Code extension and Docker Engine.

I’ve cleared my colima and docker versions and installed a slightly older version of colima and docker via direct download.

colima version v0.8.1
git commit: 96598cc5b64e5e9e1e64891642b91edc8ac49d16

runtime: docker
arch: aarch64
client: v27.4.0
server: v27.4.0

This then allowed the Cloud code extension to detect the running emulator

Since this was working I updated Colima to the latest version (0.9.1 via brew) and the extension was able to detect the containers ok.

I did the same to docker engine and the extension could detect a emulator with Docker Engine v28.5.2

colima version 0.9.1
git commit: 0cbf719f5409ce04b9f0607b681c005d2ff7d94a

runtime: docker
arch: aarch64
client: v28.5.2
server: v28.4.0

I then did the same with the latest version of docker available via brew and direct download and the extension couldn’t detect a running container of any version of the emulator I’ve tested.

colima version 0.9.1
git commit: 0cbf719f5409ce04b9f0607b681c005d2ff7d94a

runtime: docker
arch: aarch64
client: v29.0.4
server: v28.4.0                                                                                                                                                                                   

[rabustamante]

Jordan,

It seems likely that this issue is stemming from a mismatch between version 28.x and 29.x, I found that there is some changes to the docker output that could be causing this Field name changed from ApiVersion to APIVersion in Docker 29.0.0 JSON output · Issue #6647 · docker/cli · GitHub

Are you able to use the version on the Docker client that works in the meantime?

I think this is something that may need to be reported as an issue. Cloud Clode Issues

[Jordan_Hood]

Hi Rabustamante

Using v28 Docker client is fine for me until v29 is supported.

Happy to raise a issue on Cloud Code when I get a moment