podman-compose: Don't wrap podman
Podman is now a wrapped with it's container runtimes in the podman closure. This means that the podman passed to podman-compose is not necessarily the one that the user wants to use as it lacks user configured container runtimes. This change aims to make package composition more intuitive by defering the installation of podman to the user of podman-compose.
This commit is contained in:
parent
e061c4bab3
commit
0c70afa6d1
@ -1,4 +1,4 @@
|
||||
{ lib, buildPythonApplication, fetchPypi, podman, pyyaml }:
|
||||
{ lib, buildPythonApplication, fetchPypi, pyyaml }:
|
||||
|
||||
buildPythonApplication rec {
|
||||
version = "0.1.5";
|
||||
@ -9,7 +9,7 @@ buildPythonApplication rec {
|
||||
sha256 = "1sgbc889zq127qhxa9frhswa1mid19fs5qnyzfihx648y5i968pv";
|
||||
};
|
||||
|
||||
propagatedBuildInputs = [ pyyaml podman ];
|
||||
propagatedBuildInputs = [ pyyaml ];
|
||||
|
||||
meta = {
|
||||
description = "An implementation of docker-compose with podman backend";
|
||||
|
Loading…
Reference in New Issue
Block a user