It seems lsb_release is not installed.

you can install it via

    apt-get update &amp;&amp; apt-get install -y lsb-release &amp;&amp; apt-get clean all

Hope that helps ;)

This error can happen due to uninstalling or upgrading the default python3 program version in ubuntu 16.04 

The way to correct this is by reinstalling the original python3 version which comes with ubuntu and relinking again. (in ubuntu 16.04 - the default python3 version is python 3.5

    sudo rm /usr/bin/python3
    sudo ln -s /usr/bin/python3.5 /usr/bin/python3



lsb_release.py lives in /usr/share/pyshared which to me doesn&#39;t look like python3.6 and above is referencing.

I found the following will create a link back from a later Python install to ths /usr/share script:

    sudo ln -s /usr/share/pyshared/lsb_release.py /usr/lib/python3.9/site-packages/lsb_release.py

[`TypeVar`](https://docs.python.org/3/library/typing.html#typing.TypeVar) and [`NewType`](https://docs.python.org/3/library/typing.html#newtype) seem related but I&#39;m not sure when I&#39;m supposed to use each or what the difference is at runtime and statically.

What is the difference between TypeVar and NewType?

I&#39;m running a workflow on some Operating systems.

However, there is a specific step that I have to run only on Ubuntu:

    runs-on: ${{ matrix.os }}
    strategy:
        matrix:
            os: [ubuntu-latest, windows-latest, macOS-latest]
    steps:
        - name: Setup Ubuntu
          run : export DISPLAY=&quot;127.0.0.1:10.0&quot;
          if: # --&gt; What should be here? &lt;--
I couldn&#39;t find any examples nor explanation on how to run steps on specific OSes. 

Can somebody help?

Github Actions: Run step on specific OS

I just wanted to test something out real quick. So I ran a docker container and I wanted to check which version I was running:

    $ docker run -it ubuntu    
    root@471bdb08b11a:/# lsb_release -a
    bash: lsb_release: command not found
    root@471bdb08b11a:/# 

So I tried installing it (as [suggested here][1]):

    root@471bdb08b11a:/# apt install lsb_release
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    E: Unable to locate package lsb_release
    root@471bdb08b11a:/# 

Anybody any idea why this isn&#39;t working?

  [1]: http://www.andryhacks.com/bash-lsb_release-command-not-found/

lsb_release: command not found in latest Ubuntu Docker container

I just wanted to test something out real quick. So I ran a docker container and I wanted to check which version I was running:
<pre><code class="hljs language-ruby">$ docker run -it ubuntu 
root@471bdb08b11a:/# lsb_release -a
bash: lsb_release: command not found
root@471bdb08b11a:/# 
</code></pre>
So I tried installing it (as <a href="http://www.andryhacks.com/bash-lsb_release-command-not-found/" target="_blank" rel="noopener noreferrer">suggested here</a>):
<pre><code class="hljs language-ruby">root@471bdb08b11a:/# apt install lsb_release
Reading package lists... Done
Building dependency tree 
Reading state information... Done
E: Unable to locate package lsb_release
root@471bdb08b11a:/# 
</code></pre>
Anybody any idea why this isn't working?

I was implementing a hashmap in C as part of a project I&#39;m working on and using random inserts to test it.  I noticed that `rand()` on Linux seems to repeat numbers far more often than on Mac. `RAND_MAX` is `2147483647/0x7FFFFFFF` on both platforms. I&#39;ve reduced it to this test program that makes a byte array `RAND_MAX+1`-long, generates `RAND_MAX` random numbers, notes if each is a duplicate, and checks it off the list as seen.

```
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;string.h&gt;
#include &lt;time.h&gt;

int main() {
    size_t size = ((size_t)RAND_MAX) + 1;
    char *randoms = calloc(size, sizeof(char));
    int dups = 0;
    srand(time(0));
    for (int i = 0; i &lt; RAND_MAX; i++) {
        int r = rand();
        if (randoms[r]) {
            // printf(&quot;duplicate at %d\n&quot;, r);
            dups++;
        }
        randoms[r] = 1;
    }
    printf(&quot;duplicates: %d\n&quot;, dups);
}
```

Linux consistently generates around 790 million duplicates. Mac consistently only generates one, so it loops through every random number that it can generate *almost* without repeating. Can anyone please explain to me how this works? I can&#39;t tell anything different from the `man` pages, can&#39;t tell which RNG each is using, and can&#39;t find anything online. Thanks!

Why does rand() repeat numbers far more often on Linux than Mac?

Good afternoon, please tell me what I&#39;m doing wrong. I just installed the Linux Ubuntu on my computer and still don’t understand anything about it. I tried to install PostreSQL and pgAdmin. I installed on this video tutorial `https://www.youtube.com/watch?v=Vdzb7JTPnGk` I get this error.

Text of Error: `Skipping acquire of configured file &#39;main/binary-i386/Packages&#39; as repository &#39;http://apt.postgresql.org/pub/repos/apt focal-pgdg InRelease&#39; doesn&#39;t support architecture &#39;i386&#39;`

  ![](https://i.stack.imgur.com/tm6Gr.png)

Tell me please how to fix it. 
My version of ubuntu: `Ubuntu 20.04 LTS`




Skipping acquire of configured file &#39;main/binary-i386/Packages&#39;

How do I install python3 and python3-pip on an alpine based image (without using a python image)?

```
 $ apk add --update python3.8 python3-pip
 ERROR: unsatisfiable constraints:
   python3-pip (missing):
     required by: world[python3-pip]
   python3.8 (missing):
     required by: world[python3.8]
```

How do I install python on alpine linux?

I want to install this module but there is something wrong when I try the step `docker-compose build ...`

I tried to update the Docker version and restart Docker many times. But it didn&#39;t work.

```
git clone https://github.com/uhh-lt/158.git
cd 158
docker-compose build
```


```
File &quot;/home/ming/.local/bin/docker-compose&quot;, line 8, in &lt;module&gt;
    sys.exit(main())
  File &quot;/home/ming/.local/lib/python3.8/site-packages/compose/cli/main.py&quot;, line 67, in main
    command()
  File &quot;/home/ming/.local/lib/python3.8/site-packages/compose/cli/main.py&quot;, line 123, in perform_command
    project = project_from_options(&#39;.&#39;, options)
  File &quot;/home/ming/.local/lib/python3.8/site-packages/compose/cli/command.py&quot;, line 60, in project_from_options
    return get_project(
  File &quot;/home/ming/.local/lib/python3.8/site-packages/compose/cli/command.py&quot;, line 131, in get_project
    client = get_client(
  File &quot;/home/ming/.local/lib/python3.8/site-packages/compose/cli/docker_client.py&quot;, line 41, in get_client
    client = docker_client(
  File &quot;/home/ming/.local/lib/python3.8/site-packages/compose/cli/docker_client.py&quot;, line 170, in docker_client
    client = APIClient(**kwargs)
  File &quot;/home/ming/.local/lib/python3.8/site-packages/docker/api/client.py&quot;, line 188, in __init__
    self._version = self._retrieve_server_version()
  File &quot;/home/ming/.local/lib/python3.8/site-packages/docker/api/client.py&quot;, line 212, in _retrieve_server_version
    raise DockerException(
docker.errors.DockerException: Error while fetching server API version: (&#39;Connection aborted.&#39;, FileNotFoundError(2, &#39;No such file or directory&#39;))
```

#### Update 2020-11-23

Thanks for two of you helping me with the error! I tried the commend but can&#39;t connect to my Docker:

```
ming@KITM-7664:~$ sudo /etc/init.d/docker start
[sudo] password for ming:
 * Starting Docker: docker                                                                                       [ OK ]

ming@KITM-7664:~$ which docker
/usr/bin/docker

ming@KITM-7664:~$ docker version
Client: Docker Engine - Community
 Version:           19.03.13
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        4484c46d9d
 Built:             Wed Sep 16 17:02:52 2020
 OS/Arch:           linux/amd64
 Experimental:      false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

ming@KITM-7664:~$ systemctl status docker
System has not been booted with systemd as init system (PID 1). Can&#39;t operate.
Failed to connect to bus: Host is down

ming@KITM-7664:~$ systemctl start docker
System has not been booted with systemd as init system (PID 1). Can&#39;t operate.
Failed to connect to bus: Host is down

ming@KITM-7664:~$ sudo /etc/init.d/docker start
 * Starting Docker: docker                                                                                       [ OK ]

ming@KITM-7664:~$ docker version
Client: Docker Engine - Community
 Version:           19.03.13
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        4484c46d9d
 Built:             Wed Sep 16 17:02:52 2020
 OS/Arch:           linux/amd64
 Experimental:      false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```

docker.errors.DockerException: Error while fetching server API version

I just updated to the new version of Go - Go version 1.16.2 Linux/amd64 and am getting an error when I build a [Hello, World! example][1]:

&gt; go: go.mod file not found in current directory or any parent directory; see &#39;go help modules&#39;

Even when I follow the fix from [that post][2] it isn&#39;t working. I set these variables and then build again:

```lang-none
GO111MODULE=on
GOPROXY=https://proxy.golang.org,direct
```

And the same problem unfortunately.

  [1]: https://tour.golang.org/welcome/1
  [2]: https://stackoverflow.com/questions/66740187/errors-running-first-go-project-on-local-machine




Error message &quot;go: go.mod file not found in current directory or any parent directory; see &#39;go help modules&#39;&quot;

When building a docker image you normally use `docker build .`.

But I&#39;ve found that you can specify `--pull`, so the whole command would look like `docker build --pull .`

I&#39;m not sure about the purpose of `--pull`. Docker&#39;s [official documentation][1] says &quot;Always attempt to pull a newer version of the image&quot;, and I&#39;m not sure what this means in this context.

You use `docker build` to build a new image, and eventually publish it somewhere to a container registry. Why would you want to pull something that doesn&#39;t exist yet?

  [1]: https://docs.docker.com/engine/reference/commandline/build/

What&#39;s the purpose of &quot;docker build --pull&quot;?

I tried `export DOCKER_BUILDKIT=1` before a `docker-compose build` command and I did not see the expected BuildKit output. What did I miss?

How do you enable BuildKit with docker-compose?

I have the following Dockerfile that uses the latest Ubuntu image pulled from dockerhub:

    FROM ubuntu:latest  
    RUN apt-get update  &amp;&amp; apt-get install -y  g++ llvm lcov 

when I launch the docker build command, the following errors occur: 

&gt;Err:2 http://archive.ubuntu.com/ubuntu bionic InRelease 
At least one invalid signature was encountered.

&gt;Err:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
  At least one invalid signature was encountered.

&gt;Err:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
  At least one invalid signature was encountered.

&gt;Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  At least one invalid signature was encountered.

&gt;Reading package lists...

&gt;W: GPG error: http://archive.ubuntu.com/ubuntu bionic InRelease: At least one invalid signature was encountered.
E: The repository &#39;http://archive.ubuntu.com/ubuntu bionic InRelease&#39; is not signed.

&gt;W: GPG error: http://security.ubuntu.com/ubuntu bionic-security InRelease: At least one invalid signature was encountered.
E: The repository &#39;http://security.ubuntu.com/ubuntu bionic-security InRelease&#39; is not signed.

&gt;W: GPG error: http://archive.ubuntu.com/ubuntu bionic-updates InRelease: At least one invalid signature was encountered.
E: The repository &#39;http://archive.ubuntu.com/ubuntu bionic-updates InRelease&#39; is not signed.

&gt;W: GPG error: http://archive.ubuntu.com/ubuntu bionic-backports InRelease: At least one invalid signature was encountered.
E: The repository &#39;http://archive.ubuntu.com/ubuntu bionic-backports InRelease&#39; is not signed.

I read here https://superuser.com/questions/1331936/how-can-i-get-past-a-repository-is-not-signed-message-when-attempting-to-upgr that you can pass this error using --allow-unauthenitcated or --allow-insecure-repositories but both seem to me workarounds that may compromize security of the container. 

**EDIT**

Tried to pull ubuntu:18.04, ubuntu:19:04, ubuntu:19.10 same error with different distro name

Repository is not signed in docker build

Can anyone help me with this problem.

When i try to create a docker image from a dockerfile for laravel application i get this error:

    

&gt; checking for oniguruma... no
&gt;     configure: error: Package requirements (oniguruma) were not met:
&gt;     
&gt;     No package &#39;oniguruma&#39; found
&gt;     
&gt;     Consider adjusting the PKG_CONFIG_PATH environment variable if you
&gt;     installed software in a non-standard prefix.
&gt;     
&gt;     Alternatively, you may set the environment variables ONIG_CFLAGS
&gt;     and ONIG_LIBS to avoid the need to call pkg-config.
&gt;     See the pkg-config man page for more details.
&gt;    The command &#39;/bin/sh -c docker-php-ext-install pdo mbstring&#39; returned a non-zero code: 1


Here is my Dockerfile:


    FROM php:7
    RUN apt-get update -y &amp;&amp; apt-get install -y openssl zip unzip git
    RUN curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer
    RUN docker-php-ext-install pdo mbstring
    WORKDIR /app
    COPY app /app # this copies all the app files to a folder called `app`
    RUN composer install
    
    CMD php artisan serve --host=0.0.0.0 --port=8000
    EXPOSE 8000

and the docker command to build the Dockerfile

    sudo docker build -t test .

Docker &amp; Laravel : configure: error: Package requirements (oniguruma) were not met

I cannot start keycloak container using ansible and docker-compose. I&#39;am getting error: User with username &#39;admin&#39; already added to &#39;/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json&#39;

I have 3 ansible jobs:

Create netwrok:

```
- name: Create a internal network
  docker_network:
    name: internal
```

Setup postgres:

```
- name: &quot;Install Postgres&quot;
  docker_compose:
    project_name: posgressdb
    restarted: true
    pull: yes
    definition:
      version: &#39;2&#39;
      services:
        postgres:
          image: postgres:12.1
          container_name: postgres
          restart: always
          env_file:
            - /etc/app/db.env
          networks:
            - internal
          volumes:
            - postgres-data:/var/lib/postgresql/data
            - /etc/app/createdb.sh:/docker-entrypoint-initdb.d/init-app-db.sh
          ports:
            - &quot;5432:5432&quot;
      volumes:
        postgres-data:
      networks:
        internal:
          external:
            name: internal
```

Create keycloak container:

```
- name: Install keycloak
  docker_compose:
    project_name: appauth
    restarted: true
    pull: yes
    definition:
      version: &#39;2&#39;
      services:
        keycloak:
          image: jboss/keycloak:8.0.1
          container_name: keycloak
          restart: always
          environment:
            - DB_VENDOR=POSTGRES
            - DB_ADDR=postgres
            - DB_PORT=5432
            - DB_SCHEMA=public
            - DB_DATABASE=keycloak
            - DB_USER=keycloak
            - DB_PASSWORD=keycloak
            - KEYCLOAK_USER=admin
            - KEYCLOAK_PASSWORD=admin
          networks:
            - internal
      networks:
        internal:
          external:
            name: internal

```

Does anyone have any idea why I get this error?

**EDIT**

If I downgrade keycloak to version 7 it starts normally!

Keycloak 8: User with username &#39;admin&#39; already added

I have a live server and development box, call them live and dev respectively both running postgresql. I can see both and manage both with pgadmin4 without trouble, and both are fully functional the one behing a live website and the other when I run by website in debug mode on the my dev box. Pretty ordinary setup.

For years I have been running the same bash script I wrote that dumps the live database then restores it on the dev box so I have the latest live snapshot to work with.

Today this fails me with the titled message:
```
pg_restore: [archiver] unsupported version (1.14) in file header
```

I have tried to diagnose this, and searched extensively on-line but am bedeviled and have failed so here I am cap in hand for expertise.

To help I will share the following:

```
$ pg_dump --version
pg_dump (PostgreSQL) 10.11 (Ubuntu 10.11-1.pgdg18.04+1)
$ pg_restore --version
pg_restore (PostgreSQL) 10.11 (Ubuntu 10.11-1.pgdg18.04+1)
$ pg_dump --host=live.lan --port=5432 --dbname=mydb --username=myuser --format=custom &gt; test.backup
$ ls -l test.backup 
-rw-r--r-- 1 bernd bernd 2398358 Dec 23 23:40 test.backup
$ file test.backup 
test.backup: PostgreSQL custom database dump - v1.14-0
$ pg_restore --dbname=mydb test.backup 
pg_restore: [archiver] unsupported version (1.14) in file header
```

Given pg_dump and pg_restore are identical versions and:

```
$ which pg_dump
/usr/bin/pg_dump
$ which pg_restore
/usr/bin/pg_restore
$ ls -l /usr/bin/pg_dump /usr/bin/pg_restore
lrwxrwxrwx 1 root root 37 Nov 14 23:23 /usr/bin/pg_dump -&gt; ../share/postgresql-common/pg_wrapper
lrwxrwxrwx 1 root root 37 Nov 14 23:23 /usr/bin/pg_restore -&gt; ../share/postgresql-common/pg_wrapper
```

I can see they are not just identical versions but are run by the same wrapper script (which happens to be a perl script - now that&#39;s a language you don&#39;t see much anymore and I used to code in extensively)

So I&#39;m left totally perplexed. Thinking there may be a version issue with the live machine:

```
$ ssh live.lan
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-72-generic x86_64)
$ which pg_dump
/usr/bin/pg_dump
$ which pg_restore
/usr/bin/pg_restore
$ pg_dump --version
pg_dump (PostgreSQL) 10.10 (Ubuntu 10.10-0ubuntu0.18.04.1)
$ pg_restore --version
pg_restore (PostgreSQL) 10.10 (Ubuntu 10.10-0ubuntu0.18.04.1)
```

I can see the live box does have slightly older version of pg_dump (which would only matter if pg_dump on my dev box somehow used a RPC to the live box to run its pg_dump).

Now there is maybe a small clue in the fact that my dev box has seen a few postgresql upgrades come through and so for example:

```
$ pg_lsclusters
Ver Cluster Port Status Owner    Data directory              Log file
10  main    5432 online postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
11  main    5433 online postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11-main.log
12  main    5434 online postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log
```

The 11 and 12 clusters remain unused as evidenced by empty log files. I&#39;m using 10. But I do notice that:

```
$ psql --version
psql (PostgreSQL) 12.1 (Ubuntu 12.1-1.pgdg18.04+1)
$ ssh live.lan
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-72-generic x86_64)
$ psql --version
psql (PostgreSQL) 10.10 (Ubuntu 10.10-0ubuntu0.18.04.1)
```

which is mildly fishy but again not obviously a cause or related:

 1. I am using pg_dump not psql
 2. I am using only the dev boxes pg tools not the live boxes (they should be irrelevant, the whole data transfer theoretically over port 5432 on the live box which delivers a databse dump to pg_dump on my dev box.

Here are the clusters on the love box and it&#39;s over port 5432 that on live.lan I&#39;m running pg_dump!

```
$ pg_lsclusters 
Ver Cluster Port Status Owner    Data directory           Log file
10  main    5432 online postgres /data/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
```

I am deeply perplexed and hamstrung at present by this. Would deeply appreciate forward moving clues. If I am compelled to fish around in the dark I will probbaly uninstall postgres 11 and 12 again and see if that helps, else I will end up having to trace `/usr/share/postgresql-common/pg_wrapper` to see how and where the two paths of pg_dump and pg_restore diverge down incompatible version paths. 

**Update:**

A further clue I have uncovered, that permits me a workaround but simply deepens the mystery is as follows:

```
$ sudo -u postgres pg_dump --host=live.lan --port=5432 --dbname=mydb --username=myuser --format=custom &gt; test.backup
$ sudo -u postgres /usr/lib/postgresql/10/bin/pg_dump --host=live.lan --port=5432 --dbname=mydb --username=myuser --format=custom &gt; test2.backup
$ sudo -u postgres pg_restore -l test.backup
pg_restore: [archiver] unsupported version (1.14) in file header
$ sudo -u postgres pg_restore -l test2.backup
... produces listing of contents ...
$ sudo -u postgres pg_dump --version
pg_dump (PostgreSQL) 10.11 (Ubuntu 10.11-1.pgdg18.04+1)
$ sudo -u postgres /usr/lib/postgresql/10/bin/pg_dump --version
pg_dump (PostgreSQL) 10.11 (Ubuntu 10.11-1.pgdg18.04+1)
```

That is perplexing beyond belief. The only possible explanations:

 1. in spite of reporting identical version numbers the two pg_dumps are different. I would rule this out as beyond belief.
 2. pg_dump runs pg_wrapper which runs /usr/lib/postgresql/10/bin/pg_dump with some mystery argument(s) that break it! 

The second is plausible, and will require me to instrument pg_wrapper to diagnose. 

**Update 2:**

And one instrumentation of pg_wrapper later. It eventuates that pg_dump runs pg_wrapper which runs `/usr/lib/postgresql/12/bin/pg_dump` yet it runs `/usr/lib/postgresql/10/bin/pg_restore` ... Go figure! Starting to think this a postgresql version interoperability bug!

**Update 3:**

Looking deeper into `pg_wrapper`, nailed the cause, and yes I&#39;d argue it&#39;s a pg_wrapper bug of a kind though it may be debatable, hardly though IMHO. Here&#39;s what it does:

If `--host` is provided then it uses the newest version of postgresql installed (12 in my case and this is for pg_dump, so pg_dump 12 creates the dump)

If `--host` is not provided then it consults the user config (10 in my case, and this is for pg_restore, so pg_restore 10 is run and it can&#39;t read a file created by pg_dump 12).

So why is this a bug? Because I have a use config, and I&#39;d like it respected whether or not I&#39;m talking to a remote host. More to the point if I specify a host I certainly don&#39;t expect to use the latest local version ignoring local config. I&#39;d expect either to respect local config (as is the case when no remote host is specified) or try to match the rmeote hosts version. Arbitrarily leaning on the latest installed version is IMHO deeply questionable.

BUT it turns out there is a workaround that works. Essentially instead of:

```
sudo -u postgres pg_restore -l test.backup
```

this works:

```
sudo -u postgres pg_restore --host=localhost -l test.backup
```

By specifying the host ironically we force it to ignore local configs and use the newest version of pg_restore which seems to work fine restoring to a PG 10 cluster. 

pg_restore: [archiver] unsupported version (1.14) in file header

After upgrading from WSL to WSL2 

    sudo apt-get update

not works any longer. After: 

`wsl --set-version Ubuntu-18.04 2`


Output is:

    &gt; sudo apt-get update
    Err:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
      Temporary failure resolving &#39;security.ubuntu.com&#39;
    Err:2 http://archive.ubuntu.com/ubuntu bionic InRelease
      Temporary failure resolving &#39;archive.ubuntu.com&#39;
    Err:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
      Temporary failure resolving &#39;archive.ubuntu.com&#39;
    Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
      Temporary failure resolving &#39;archive.ubuntu.com&#39;
    Reading package lists... Done
    W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease  Temporary failure resolving &#39;archive.ubuntu.com&#39;
    W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease  Temporary failure resolving &#39;archive.ubuntu.com&#39;
    W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease  Temporary failure resolving &#39;archive.ubuntu.com&#39;
    W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease  Temporary failure resolving &#39;security.ubuntu.com&#39;
    W: Some index files failed to download. They have been ignored, or old ones used instead.

After going back to WSL1 the problem disappears again. Same on Debian and analogous in CentOS .. so WSL2 must have a bug.

The Windows10 build Version is 19041 and was installed today.

Any work around for WSL2?
Regards



Windows10 WSL2 Ubuntu / Debian # no network

I recently upgraded my OS to Ubuntu 20.04 LTS. 

Now when I try to import a library like Numpy in Python, I get the following error:

```
ImportError: libffi.so.6: cannot open shared object file: No such file or directory
```

I tried installing the `libffi` package, but apt can&#39;t locate it :

```
sudo apt-get install libffi
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package libffi
```

Ubuntu 20.04 upgrade, Python missing libffi.so.6

I created a conda environment with Python version 3.8, but it doesn&#39;t support matplotlib... So I am looking for something like this to change the Python version: `conda env my_env update to python=3.6`. Is this possible or do I need to recreate the environment?

I have miniconda installed.

Content Type	Original Author	Original Content on Stackoverflow
Question	kramer65	View Question on Stackoverflow
Solution 1 - Linux	ckaserer	View Answer on Stackoverflow
Solution 2 - Linux	Magnus Melwin	View Answer on Stackoverflow
Solution 3 - Linux	Julian Robbins	View Answer on Stackoverflow

lsb_release: command not found in latest Ubuntu Docker container

Linux Problem Overview

Linux Solutions

Solution 1 - Linux

Solution 2 - Linux

Solution 3 - Linux

Github Actions: Run step on specific OS

What is the difference between TypeVar and NewType?

Attributions