slim | Simple Login Manager ) is a graphical login manager | Identity Management library

You just need to know, which menu is open then! I have used simple global variable menu to find which menu is open. After declaring menu as 0, if something from drop-down is selected menu is changed to 1 for minutes and 2 for seconds:

There are two issues here:

1. Oracle Database is not supported on ARM processors, only Intel. See here: https://github.com/oracle/docker-images/issues/1814
2. Oracle Database Docker images are only supported with Oracle Linux 7 or Red Hat Enterprise Linux 7 as the host OS. See here: https://github.com/oracle/docker-images/tree/main/OracleDatabase/SingleInstance

Oracle Database ... is supported for Oracle Linux 7 and Red Hat Enterprise Linux (RHEL) 7. For more details please see My Oracle Support note: Oracle Support for Database Running on Docker (Doc ID 2216342.1)

The referenced My Oracle Support Doc ID goes on to say that the database binaries in their Docker image are built specifically for Oracle Linux hosts, and will also work on Red Hat. That's it.

Linux being what it is (flexible), lots of people have gotten the images to run on other flavors like Ubuntu with a bit of creativity, but only on x86 processors and even then the results are not guaranteed by Oracle: you won't be able to get support or practical advice when (and it's always when, not if in IT) things don't work as expected. You might not even be able to tell when things aren't working as they should. This is a case where creativity is not particularly rewarded; if you want it to work and get meaningful help, my advice is to use the supported hardware architecture and operating system version. Anything else is a complete gamble.

The way your container is built doesn't add a user, so everything is done as root.

You could create a user and install to that users's home directory by doing something like this;

It happened the same to me last friday. I think it has something to do with Cuda instalation in Google Colab but I don't know exactly the reason

Your issue is, I think, with your requirements file. In that you include bson as a dependency, which is also included in the pymongo library. See this question. Removing it seems to solve the issue:

Both plots actually use the same width, in that the boxes take up the same x-axis range in both. You can see that the extent of the box is from 0.90 to 1.10 in the second plot - so it spans the 0.2 width that you've asked for.

What's different is that, since the second plot only has one data point, the (automatically chosen) visual span of the x-axis is much smaller. At a glance, the first plot seems to be showing from x = 0.8 to 2.2, so the 0.2 width is relatively slim. The second plot is only showing from something like 0.89 to 1.11, so a 0.2 width is actually a big chunk of that.

To make the box visually slim in the second plot, you can set the x-axis limits with xlims!:

It seems that you have problems with peer dependencies, if you just set your npm to use legacy dependency logic to install your packages you will solve the problem.

Just add to your Dockerfile this setting before running npm install:

Mount your script files directly in the container via docker-compose.yml: