Skip to content

gitpod-classic is not available anymore, so the demo doesnt work anymore out of the box #3532

@Sebigamer4

Description

@Sebigamer4

Description

As in the description, gitpod is now ona, but the config files for gitpod are in the now called gitpod-classic format.

they can be automatically migrated via the gitpod cli, as stated here
https://ona.com/docs/ona/configuration/migrate-from-classic

I tried that, and it looks promising.

One thing to note: the migration changes is the base container for the env (in the .gitpod.Dockerfile), so you need to manually revert that change, since in the automatically selected ubuntu image, the sdkman tool is missing.

Another issue ive encountered then was a missing publickey in aptitude for postgres,
but that was easily fixed by retrieving it manually before the apt commands with the following line

RUN sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 7FCC7D46ACCC4CF8

before the RUN curl -o odoo.deb .....

Then i was able to build the dev container and enter it.
After that, i also got the 4 Tasks (task 0-3)

But now, other issues stack up with the tasks.

Maybe someone with more insight about the environnement could have a look into it?

I dont think that there are big issues, it just needs to be brought up to date

Screenshots

No response

Operating System

No response

How to reproduce the Error?

Follow the instructions in the documentation

https://openems.github.io/openems.io/openems/latest/simulation/gitpod.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions