Control: reassign -1 podman-compose
Control: affects -1 = src:libpod
On Sun, Sep 01, 2024 at 01:08:07PM +0100, James Addison wrote:
> In #1054460 a duplicate-file conflict on the podman-compose.1 manual was
> resolved: the manual was dropped from the podman binary package and the
> version from po
Control: reassign -1 src:passt 0.0~git20240814.61c0b0d-1
Control: affects -1 podman
Control: severity -1 serious
Control: retitle -1 passt broken on i386, possibly all 32-bit architectures
On Sun, Aug 18, 2024 at 04:47:39PM +0200, Uroš Knupleš wrote:
> Using podman in a rootless environment (such
Control: reassign -1 crun
Control: retitle -1 Ship the crun-wasm runtime
Control: severity -1 wishlist
Control: forwarded -1 https://github.com/containers/crun/issues/1468
On Sun, May 12, 2024 at 03:34:42PM +0300, Faidon Liambotis wrote:
> Perhaps it's worth bringing it up with both
On Sat, May 11, 2024 at 11:16:00AM -0400, Reinhard Tartler wrote:
> > I see three paths forward:
> > 1) We do the same, creating a new (almost) empty package.
> > 2) We ship a /usr/bin/crun-wasm symlink in the crun package.
> > 3) We patch podman to use /usr/bin/crun instead of, or in addition to,
Control: tags -1 confirmed
On Wed, May 08, 2024 at 03:10:40AM +0300, Eugen Stan wrote:
> I followed the guide to run wasm images on my system and it failed with
> errors.
>
> I believe the issue is that podman looks for crun-wasm binary by default.
> I failed to configure podman to use crun inste
Control: tags -1 + moreinfo
On Wed, Mar 13, 2024 at 12:17:12AM +0100, Antoine Sirinelli wrote:
> When I create a new custom network, the dns is not enabled:
>
> $ podman network create test
> test
> $ podman network inspect test
>
> [...]
>
> The outcome should have "dns_enabled" to true.
Per p
On Sat, Mar 09, 2024 at 06:44:56AM -0700, Anthony Fok wrote:
> Package: podman
> Version: 4.9.3+ds1-1
> Severity: normal
>
> [...]
>
> Eventually, I ran the following commands to remedy the situation:
>
> sudo apt install containers-storage
> rm -rf ~/.local/share/containers
> podman s
On Mon, Feb 05, 2024 at 02:13:50PM +0800, 张家岭 wrote:
> Hi, this can support loong64 build , Ｉ build this in my local . and I'll
> submit to upstream .
But is your patch necessary to build for loong64? Does the build fail
without your patch?
Faidon
__
Control: tags -1 upstream moreinfo
On Fri, Feb 02, 2024 at 04:40:08AM +, JiaLing Zhang wrote:
> Please help to add support for loong64.I have build it in my local
> machine.
Unless I'm missing something, both of your changes seem... unrelated to
what we ship in Debian. Have you verified that
Control: reassign -1 src:golang-github-containers-storage 1.43.0+ds1-8
Control: fixed -1 1.48.1+ds1-1
On Wed, Jan 31, 2024 at 03:45:35PM +0100, Holger Leskien wrote:
> at the moment the dependency on the containers-storage package is "suggests"
> only. However, this means that the package is not i
Control: reassign -1 src:golang-github-containers-storage 1.43.0+ds1-8
Control: fixed -1 1.45.1+ds1-1
Control: affects -1 src:libpod
On Sun, Jan 21, 2024 at 01:17:46AM +0800, Tee Hao Wei wrote:
> Oh. I just noticed how Debian handles Go dependencies..
>
> I guess this will actually need to be a c
branch (itself a backport from v4.3.0), to
+address an incorrect handling of supplementary groups. (Closes: #1019591)
+ * Add myself to Uploaders.
+
+ -- Faidon Liambotis Fri, 29 Dec 2023 17:26:49 +0200
+
libpod (3.0.1+dfsg1-3+deb11u4) bullseye; urgency=medium
* Recompile to fix parsi
Hi folks,
TL;DR, please mark CVE-2023-0778 as not affecting bullseye.
I was looking into CVE-2023-0778, a vulnerability in podman
(src:libpod). The vulnerability's description is:
> This issue may allow a malicious user to replace a normal file in a
> volume with a symlink while exporting the vol
Control: tags -1 moreinfo
On Wed, Apr 19, 2023 at 09:24:21AM +0800, 鐘翊修 wrote:
> following man 5 containers-storage.conf,
> when a system have both /etc/containers/storage.conf and
> /usr/share/containers/storage.conf
>
> the values in /etc/containers/storage.conf overwrite the value in
> /usr/
On Sun, Jun 04, 2023 at 02:52:56PM +0200, Felix Stupp wrote:
> the current version of podman does not allow me to run any container due
> to the following error message:
> Error: stat /home/$USER/.config/docker/config.json: no such file or directory
>
> I can trigger this issue with a simple: podm
Package: podman
Version: 4.3.1+ds1-8+b1
Severity: minor
Linux 5.13+ (so Debian stable+) added user namespace support to
overlayfs. Podman can leverage that and use overlayfs in rootless
containers, which results into performance benefits compared to
fuse-overlayfs.
See this older RedHat article f
On Fri, Aug 19, 2022 at 02:16:19PM +0200, Andrej Shadura wrote:
> > I have to respectfully disagree here. In Debian, "Recommends"
> > relationships are installed by default, and your message indicates to me
> > that you have configured your system to not install them. It furthermore
> > seems to me
On Wed, Apr 21, 2021 at 09:41:47PM +, Reinhard Tartler wrote:
>
> Add depends in iptables (Closes: #987207)
>
I recently tried to upgrade podman in
On Thu, Jan 14, 2021 at 01:29:06PM -0300, Antonio Terceiro wrote:
> On Sat, Jan 09, 2021 at 12:58:05PM +0200, Faidon Liambotis wrote:
> > On Thu, Dec 31, 2020 at 01:39:52PM -0500, Reinhard Tartler wrote:
> > > As I thought. Experimental has version 2.2, unstable/testing curren
Hi there,
On Thu, Dec 31, 2020 at 01:39:52PM -0500, Reinhard Tartler wrote:
> As I thought. Experimental has version 2.2, unstable/testing currently 2.1
> What you are asking for is one (maybe the?) major new feature introduced in
> 2.2.0.
That's helpful! I was wondering what your plans were with
20 matches
Mail list logo
