| 2023-10-13 19:35:29 |
Lucas Detje |
description |
After the recent update of ubuntu:rolling to point to mantic we noticed that one of our package scripts that relies on checking the version of dpkg-shlibdeps failed with the following error message:
`error: cannot read debian/control: No such file or directory`
It worked (and still works) on ubuntu:lunar.
The issue can be reproduced with the following Dockerfile:
```
ARG variant
FROM ubuntu:${variant}
RUN apt-get update && apt-get install -y --no-install-recommends dpkg-dev
RUN dpkg-shlibdeps --version
```
And then the following succeeds:
```
docker build --build-arg variant=lunar-20231004 .
```
While the following fails with the above mentioned error:
```
docker build --build-arg variant=mantic-20231011 .
```
Running the mantic version with a perl debugger shows that the following line which is added in the mantic version is the cause:
```
my $control = Dpkg::Control::Info->new();
``` |
After the recent update of ubuntu:rolling to point to mantic we noticed that one of our package scripts that relies on checking the version of dpkg-shlibdeps failed with the following error message:
`error: cannot read debian/control: No such file or directory`
It worked (and still works) on ubuntu:lunar.
The issue can be reproduced with the following Dockerfile:
```
ARG variant
FROM ubuntu:${variant}
RUN apt-get update && apt-get install -y --no-install-recommends dpkg-dev
RUN dpkg-shlibdeps --version
```
And then the following succeeds:
```
docker build --build-arg variant=lunar-20231004 .
```
While the following fails with the above mentioned error:
```
docker build --build-arg variant=mantic-20231011 .
```
Running the mantic version with a perl debugger shows that the following line which is added in the mantic version is the cause:
```
my $control = Dpkg::Control::Info->new();
```
Edit: This behavior was observed for linux/amd64, linux/arm/v7 and linux/arm64/v8 images if that is relevant. |
|
