Skip to content

Conversation

@Laurynas-Jagutis
Copy link
Member

Setup of the Dev Container on the Python side only.
Also has the documentation on how to set it up.

The gitattributes file is for standardizing line endings to LF instead of CRLF

Signed-off-by: Laurynas Jagutis <[email protected]>
Signed-off-by: Laurynas Jagutis <[email protected]>
Signed-off-by: Laurynas Jagutis <[email protected]>
Signed-off-by: Laurynas Jagutis <[email protected]>
Signed-off-by: Laurynas Jagutis <[email protected]>
Signed-off-by: Laurynas Jagutis <[email protected]>
Signed-off-by: Laurynas Jagutis <[email protected]>
Signed-off-by: Laurynas Jagutis <[email protected]>
Signed-off-by: Laurynas Jagutis <[email protected]>
Signed-off-by: Laurynas Jagutis <[email protected]>
@Laurynas-Jagutis Laurynas-Jagutis self-assigned this Oct 20, 2025
@Laurynas-Jagutis Laurynas-Jagutis added the feature New feature or request label Oct 20, 2025
Comment on lines +14 to +19
To begin using the container there are two open-source applications that must be installed.

* Podman (<https://podman.io/>) - a container engine that lets developers build, run, and manage containers and pods
without needing a background service.
* DevPod (<https://devpod.sh/>) - a tool that instantiates reproducible, disposable development environments allowing
developers to code inside the containers with their usual editors.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the developer need to install two additional software (besides Docker) to use the Dev Container? I am hesitating about whether this actually brings convenience to the developers.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just having docker desktop would also work (that's one tool instead of 2, but it's a paid service). Many python-only developers will have these tools installed anyways.

Devcontainers are especially useful for those python-only developers that have never worked with a C++ compiler but come from the IT industry in which containers are extremely common

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In that case, please take container into account for macOS.

https://github.com/apple/container

It is the preferred container engine.

@figueroa1395
Copy link
Member

I was able to install everything and launch the container through VScode, but I'm having trouble with python and pip. My hunch is that something went wrong because of MacOS. @Laurynas-Jagutis Let's see if we can resolve the issue together.

@figueroa1395
Copy link
Member

I was able to install everything and launch the container through VScode, but I'm having trouble with python and pip. My hunch is that something went wrong because of MacOS. @Laurynas-Jagutis Let's see if we can resolve the issue together.

After diving into the issue together with @Laurynas-Jagutis, we found that there were two issues:

  1. One must set the container from the correct branch (this branch and not main - my mistake).
  2. On MacOS (and perhaps other machines) podman has the default RAM of the containers set to a very small value, not enough to build PGM. This is very easy to solve by increasing the RAM from podman itself.

Both points will be added to the documentation, but I can now confirm that this approach works well for MacOS as well.

@TonyXiang8787
Copy link
Member

I was able to install everything and launch the container through VScode, but I'm having trouble with python and pip. My hunch is that something went wrong because of MacOS. @Laurynas-Jagutis Let's see if we can resolve the issue together.

After diving into the issue together with @Laurynas-Jagutis, we found that there were two issues:

  1. One must set the container from the correct branch (this branch and not main - my mistake).
  2. On MacOS (and perhaps other machines) podman has the default RAM of the containers set to a very small value, not enough to build PGM. This is very easy to solve by increasing the RAM from podman itself.

Both points will be added to the documentation, but I can now confirm that this approach works well for MacOS as well.

@figueroa1395 please try container app from Apple for dev container in MacOS, instead of podman/devpod

Signed-off-by: Laurynas Jagutis <[email protected]>
@sonarqubecloud
Copy link

#
# SPDX-License-Identifier: MPL-2.0

* text=auto No newline at end of file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please do not blindly set * text=auto. You can refer to https://stackoverflow.com/questions/21472971/what-is-the-purpose-of-text-auto-in-gitattributes-file

What's the reason you needed this in the first place?

@figueroa1395
Copy link
Member

I was able to install everything and launch the container through VScode, but I'm having trouble with python and pip. My hunch is that something went wrong because of MacOS. @Laurynas-Jagutis Let's see if we can resolve the issue together.

After diving into the issue together with @Laurynas-Jagutis, we found that there were two issues:

  1. One must set the container from the correct branch (this branch and not main - my mistake).
  2. On MacOS (and perhaps other machines) podman has the default RAM of the containers set to a very small value, not enough to build PGM. This is very easy to solve by increasing the RAM from podman itself.

Both points will be added to the documentation, but I can now confirm that this approach works well for MacOS as well.

@figueroa1395 please try container app from Apple for dev container in MacOS, instead of podman/devpod

I will try as soon as I have the time and report back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New feature or request

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

4 participants