I think supporting the “build:” directive on docker-compose yaml since podman can do both build and run containers
Very common use case for a large audience using docker-compose transitioning and migrating to podman to have the functionality of “docker-compose build” followed by the normal “docker-compose up”
I think is ok if it’s not supported from kube yaml pod just from a compose, since a podspec should not have any build directives
- Carlos Santana
On Feb 5, 2021, at 3:57 AM, Rudolf Vesely via Podman <firstname.lastname@example.org> wrote:
Hi Scott,I'm looking for the same functionality. If that's OK I'd like to answer your question.
If we could see the source/origin docker-compose YAML,The Yaml might get messed up so you can also get it from here: https://gist.github.com/rudolfvesely/4ad6f762eafbe5417f80ff469b690c38I intentionally made it complicated to show various options from "docker-compose".- "build: ." will use Dockerfile (in case of Podman this should be Containerfile) to build image. In other words this will run "docker build ."- "args" will define / overwrite values in "ARG" in Dockerfile/Containerfile- "dockerfile: ./foo/bar/containerfile_for_db" is used when Dockerfile has different name. In other words this will run "docker build --file=foo/bar/containerfile_for_db"$ cat ./something/api.env
NODE_ENV=test$ cat .env
TAG=v1.5$ cat docker-compose.yml
# "Dockerfile" is located in the working directory and will be used to build image
# build arguments (used in Dockerfile)
# environment variables
# "Dockerfile" has different name
# environment variables in a file
# variable defined in ".env"
- "5000:5000"Please let me know if you have other questions.Kind regards,Rudolf Vesely_______________________________________________Podman mailing list -- email@example.comTo unsubscribe send an email to firstname.lastname@example.org