Comments (5)
Yes, this is planned
We already tag the container with checksum of the the file
from podman-compose.
I'm not actually talking about building an image. I'm talking only about "rebuilding" (destroying and recreating) the container.
What I mean is, if you have a docker-compose.yml
file and you change a port forward (as an example) by adding to an existing service:
ports:
- 127.0.0.1:8080:80
And you run docker-compose up -d
then Docker will only destroy and recreate the container(s) for the service that you modified. Using the hash of the entire docker-compose.yml
file means that every service would have their containers destroyed and recreated even if only one changed.
from podman-compose.
Precise delta is difficult there are manu types of changes
- Adding containers
- removing containers
- changing details of a container
A naive implemenation, if the hash changed do down for all.
To make it precise the implementation would be
Fetch old hash from pod/first-container
If not different, don't call down
If different, list all containers and walk on them one by one checking service hash.
But currently this is not possible
Because port mapping is done on the pod not on the container
from podman-compose.
Would there be a way to tag the container with a hash of only whatever settings apply to the container? docker-compose up
will only rebuild the containers that actually changed; if you have a compose file with three containers and change the ports exposed to the host for only one container, for example, docker-compose up
will only rebuild that one container.
from podman-compose.
Build is a different matter.
If the image is there, no need for build.
from podman-compose.
Related Issues (20)
- `network_mode: none` is ignored
- Error in podman-compose up command HOT 3
- Mismatch of Documentation and Implementation of UID/GID Mappings
- compose does not use pasta network
- Error setting up OTBR ''extra spaces found" HOT 1
- podman-compose rebuilds an image that is up-to-date, pressumably for the environment set in docker-compose.yml HOT 1
- Environment handling needs integration tests
- Secrets handling needs more unit tests HOT 2
- 'podman-compose build' builds replicate images for each service in docker-compose.yaml that share a common image.
- 1.1.0 (and perhaps above) broke the use of Containerfiles HOT 1
- Error: unknown flag: --env HOT 1
- podman-compose should throw a readable error on too old python HOT 2
- All integration tests should be run automatically HOT 1
- Environment should not be set in build context HOT 2
- Detect case when port forwarding is used together with uid/gid mapping on Podman 3.4.x and issue warning HOT 4
- podman-compose up -d <container> starts other containers in the compose file
- lint checks in CI don't currently work properly.
- Release version 1.2.0 to EPEL 8 / EPEL 9 HOT 1
- Integration tests should not use network connectivity if not necessary
- Incorrect implementation of `include` HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from podman-compose.