I have recently updated docker to the latest version. (Docker engine v23.0.5).
When I start vscode insiders, the torizon early access extension just does not start.
I get a warning as follows:
Docker seem to not be enabled for current user, this will prevent many of the features of Torizon extension from working. You may add your user to the docker group or run the Torizon IDE backend with an account that is part of that group.
Also, in the Torizon IDE backend process terminal, I see an error message.
Error 530: Local Docker exception. Error while fetching server API version.
It appears you are using our V1 extensions on a Windows machine correct?
As for the issue it sounds like possibly your Windows user can’t access Docker. Maybe the Docker update messed around with the permissions. Could you see if your Windows user can run Docker commands without admin authority.
When I run “docker run hello-world” on the windows cmd command line (without admin), docker responds saying that everything is fine.
Also ran the same command on WSL (without admin) and got the same response.
Hello from Docker!
This message shows that your installation appears to be working correctly.
Just to be clear you are using the V1 extensions then? Or are you using the V2 extensions (ApolloX). I saw another question of yours on this community where you were using the V2 extensions, so I just want to be sure.
As for your issue, it sounds like Docker is running and you can use it as a non-admin user, so that’s good. So you claim these issues only started occurring after you upgraded Docker on your Windows machine, correct? Let’s try testing that theory and see if it’s really related to the Docker version or not.
Could you try rolling-back or installing a previous version of Docker on your machine. Then see if this resolves the issue or not? This would more or less confirm whether the issue is the newer Docker version or not.
Just to confirm, the extension did work before you upgraded Docker correct?
Yes the torizon early access extension did work on the windows machine with docker v4.18.0. Since the update to docker v4.19.0, it does not appear to work with it.
I have gone back to the previous version of docker v4.18.0 and the issue does seem to be resolved, although I am currently facing other bugs with this extension and was hence thinking of trying the alternative apollox.
Yes the torizon early access extension did work on the windows machine with docker v4.18.0. Since the update to docker v4.19.0, it does not appear to work with it.
In that case I guess the issue really is with the recent versions of Docker. I’ll report this to our team, for now please stick with the older version where the extension is known to work.
I am facing the same issue. How can I roll back the docker version? Just uninstall docker and reinstall 4.18?
I don’t believe Docker Desktop has a built-in rollback feature. In which case you’ll probably need to just download and install an older version.
Also, is there any documentation regarding shifting a cmakelists based V1 extension project to apollox?
We don’t have specific documentation on this. But you should be able to take the source code and copy it to the new template. Keep in mind you just want to copy the source code and related files, not the entire project itself. Since project files and configuration differ between V1 and V2.
