Add image making with custom binaries #16

New issue

Closed

opened 2023-07-14 11:46:01 +00:00 by ironbee · 2 comments

ironbee commented

2023-07-14 11:46:01 +00:00

Contributor

Perform a research and implement a way of building an aio image with custom binaries.

Current way of making a custom image for development is as follows:

make changes to a service
make its binary
build a dirty image of that service with the fresh binary
edit aio settings and use the dirty image instead of image from the registry
build a local image of aio with these settings.

We suppose that an alternative way lets us use an aio image from the registry and then swap some binaries (or just one binary) inside of it.

In terms of the files, needed changes might be implemented in

Dockerfile.custom
Makefile target make image-aio-custom.

Perform a research and implement a way of building an `aio` image with custom binaries. Current way of making a custom image for development is as follows: 1) make changes to a service 2) make its binary 3) build a dirty image of that service with the fresh binary 4) edit `aio` settings and use the dirty image instead of image from the registry 5) build a local image of `aio` with these settings. We suppose that an alternative way lets us use an `aio` image from the registry and then swap some binaries (or just one binary) inside of it. In terms of the files, needed changes might be implemented in - `Dockerfile.custom` - Makefile target `make image-aio-custom`.

ironbee self-assigned this 2023-07-14 11:46:10 +00:00

realloc commented

2023-08-02 10:41:12 +00:00

Owner

I'd suggest using dev-env for development =) AIO is not supposed to be heavily customized.

Injecting binaries into existing containers can be done by adding one more layer with that binary to existing images.

I'd suggest using dev-env for development =) AIO is not supposed to be heavily customized. Injecting binaries into existing containers can be done by adding one more layer with that binary to existing images.

alexvanin commented

2023-08-21 08:43:46 +00:00

Owner

I'd suggest using dev-env for development =) AIO is not supposed to be heavily customized.

Injecting binaries into existing containers can be done by adding one more layer with that binary to existing images.

While we use dev-env for developing, for fast fix tests in non-linux environments, this is extremely useful.

> I'd suggest using dev-env for development =) AIO is not supposed to be heavily customized. > > Injecting binaries into existing containers can be done by adding one more layer with that binary to existing images. While we use dev-env for developing, for fast fix tests in non-linux environments, this is extremely useful.

ironbee referenced this issue from a pull request that will close it,

2023-08-21 13:52:54 +00:00

[#16] Add image creation from custom binaries #25

ironbee closed this issue

2023-08-21 14:23:23 +00:00

ironbee referenced this issue from a commit

2023-08-21 14:23:24 +00:00

[#16] Add image creation from custom binaries