In order for another user to be able to run your app with a docker-compose.yml file, you need to make sure that this user has access to your custom images.
The easiest way to do this would be to push your backend and frontend images to a registry, like Docker Hub, then modify your docker-compose.yml file to reference these images in the registry.
This will allow anyone with the Compose file and access to the images to run this app using Docker Desktop.
You can find more information in the Docker documentation:
You can share the docker-compose.yml and the built images (or push them to docker hub). Others can spin it up with a simple docker-compose up -d. For backup, you can these files on multiple cloud service and can access within **moderated**.
Hi thank you benabarzua and therickward. I know I can share the images in 2 ways:
pushing them on docker hub
using podman save and share the .tar resulting file
The trouble is that when I do this, clean my computer from all images, volumes and networks with podman prune for example and I try to run the images in an other folder than the one that contains my application (the case for other users) it fails. Probably something is wrong in my compose file that obliges the app files to exist.
This most likely means you are doing your “build” step in your Compose file.
If you have a line that looks like this build: . it means you are telling Docker to build from the Dockerfile in the current directory.
What you should do to properly share your app is build and tag the required images first, then modify your Compose file to reference the already built images. This will make it possible to run your Compose file without requiring the original source files.
If you then push these images to a registry, anyone with access to this registry will be able to run your app without needing the source files.
@benabarzua is probably right, but the best way to get the best help is sharing the error message when there is one, or explaning how things fail exactly.
By the way you are using Podman, which is not Docker, but in this case it is fine as your issue is probably not related to podman.
I suspended the user. I suspected the user to be a spammer for a while already and the irrelevant link confirmed it.