Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Visual Studio Code extension unaware of 1.3, 1.4

See original GitHub issue

Expected Behavior

In Visual Studio Code, running " Azure IoT Edge: Set default IoT Edge runtime version." SHOULD IMHO list 1.3 and 1.4.

Current Behavior

Only 1.0, 1.1 and 1.2 are offered as shown in the screenshot.

Screenshot from 2022-11-14 07-28-09

Steps to Reproduce

Provide a detailed set of steps to reproduce the bug.

Open Command Palette
Run Azure IoT Edge: Set default IoT Edge runtime version.
Check content of list

Context (Environment)

Output of `iotedge check`

Click here


<Paste here between the triple backticks>

Device Information

Host OS [e.g. Ubuntu 18.04, Windows Server IoT 2019]:
Ubuntu 20.04
Architecture [e.g. amd64, arm32, arm64]:
amd64
Container OS [e.g. Linux containers, Windows containers]:
Not relevant, dev tool issue

Runtime Versions

aziot-edged [run iotedge version]:
Edge Agent [image tag (e.g. 1.0.0)]:
Edge Hub [image tag (e.g. 1.0.0)]:
Docker/Moby [run docker version]:

Note: when using Windows containers on Windows, run docker -H npipe:////./pipe/iotedge_moby_engine version instead

Logs

aziot-edged logs


<Paste here between the triple backticks>

edge-agent logs


<Paste here between the triple backticks>

edge-hub logs


<Paste here between the triple backticks>

Additional Information

Please provide any additional information that may be helpful in understanding the issue.

Issue Analytics

State:
Created 10 months ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

konichi3commented, Dec 1, 2022

Given we have published a documentation describing how to modify deployment manifest to change Edge version, we are closing the item

0reactions

PatAltimorecommented, Nov 30, 2022

Hi @TAMHAN ,

I hope you had a great trip. Yes, that’s right. You need to update your deployment manifest and change the image version to 1.4. The ellipsis … is intended to remove irrelevant sections of the manifest file. You just need to change the two “image” lines in the manifest.

The documentation update has been published. You should see a similar explanation in the article now.

Thanks, Pat

Top Results From Across the Web

Visual Studio Code July 2023

The experience when navigating between an input control (for example, search or filter input) and its results is now consistent across the Extensions...

Use the Application Accelerator Visual Studio Code ...

The Application Accelerator Visual Studio Code extension lets you explore and generate projects from the defined accelerators in Tanzu Application Platform ...

[ANN] VS Code extension 1.3 released - #16 by nilshg

Hey everyone, we just released version 1.3 of the Julia extension for VS Code, which brings a bunch of new features: Experimental native ......

Troubleshooting LSP server & VS Code extension - Learning

In one of my projects (ppx), vs code is unable to show most of the types, complains about ppxlib.metaquot extension points being unknown,...

1.2. Using Lean with VSCode

Assuming you have installed Lean and Visual Studio Code, you can add the Lean extension to VSCode by clicking the extension icon in...