Re: Docker Image Tags

Hi guys,

> Is there a reason why there's no jpa-3.8.0 or am I looking at incorrect
location [0]?

I suspect there was a mistake during the 3.8.0 release as we did not upload
the `jpa-3.8.0` image.

Quan


Vào Th 4, 8 thg 11, 2023 vào lúc 11:03 Mikhail Gryzykhin <
[email protected]> đã viết:

> Hi everyone,
>
> When I check dockerhub, I only see jpa-latest and jpa-3.7.4 (plus earlier
> versions). However I do see cassandra-3.8.0, distributed-3.8.0 and others.
>
> Is there a reason why there's no jpa-3.8.0 or am I looking at incorrect
> location [0]?
>
> Regards,
> --Mikhail
>
> ----
>
> [0] https://hub.docker.com/r/apache/james/tags?page=1&name=3.8.0
> ________________________________
> From: Rene Cordier <[email protected]>
> Sent: Tuesday, November 7, 2023 7:28 PM
> To: [email protected] <[email protected]>
> Subject: Re: Docker Image Tags
>
> [You don't often get email from [email protected]. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi Garrett,
>
> To go a bit more onto details, the tags usually are in the following
> form: james-project-3.x.x
>
> List of tags here:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fjames-project%2Ftags&data=05%7C01%7Cmgryzykhin%40concord.net%7Ca9764562aa5a47e94b2a08dbe00af1cf%7C7674c0a1b7aa4472babee8c09210b014%7C1%7C0%7C638350109849487084%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7%2F60E9Jfwb3uKrObODrqkIT5H4W7%2Bddii9OEu%2FOsqoU%3D&reserved=0
> <https://github.com/apache/james-project/tags>
>
> Then you have branches with latest fixes on releases, but maybe not
> released yet (like 3.8.x for example).
>
> The tags have the docker images uploaded on dockerhub. So:
>
> james-project-3.8.0 -> latest release, so tags with latest and 3.8.0
> (jpa-3.8.0)
>
> james-project-3.7.4 -> jpa-3.7.4
>
> ...
>
> About how to compile it, well Tung gave the answer. There is a readme as
> well explaining that at the base of the jpa-app module where the docker
> image is being built with maven and JIB:
>
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fjames-project%2Ftree%2Fmaster%2Fserver%2Fapps%2Fjpa-app&data=05%7C01%7Cmgryzykhin%40concord.net%7Ca9764562aa5a47e94b2a08dbe00af1cf%7C7674c0a1b7aa4472babee8c09210b014%7C1%7C0%7C638350109849487084%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GJSkixFG6L7NwEVRx%2F4WHEW2OthvZzT07qPbSF6Ypyw%3D&reserved=0
> <https://github.com/apache/james-project/tree/master/server/apps/jpa-app>
>
> In your case to build it on your own though, I would suggest to checkout
> the branch with active fixes on it that you want (3.8.x or 3.7.x) and
> compile it yourself with instructions above.
>
> Regards,
>
> Rene.
>
> On 11/8/23 09:16, Tung Tran Van wrote:
> > Hi,
> >
> > James is using JIB to build images (
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGoogleContainerTools%2Fjib&data=05%7C01%7Cmgryzykhin%40concord.net%7Ca9764562aa5a47e94b2a08dbe00af1cf%7C7674c0a1b7aa4472babee8c09210b014%7C1%7C0%7C638350109849487084%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=C7hMTIaUVT5LDJ03CYhQ2%2BHE57m%2FwhlbAdABDr1PAao%3D&reserved=0
> )<https://github.com/GoogleContainerTools/jib>.
> >
> > Configured at:
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fjames-project%2Fblob%2Fmaster%2Fserver%2Fapps%2Fjpa-app%2Fpom.xml%23L268&data=05%7C01%7Cmgryzykhin%40concord.net%7Ca9764562aa5a47e94b2a08dbe00af1cf%7C7674c0a1b7aa4472babee8c09210b014%7C1%7C0%7C638350109849487084%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=OYyVe27QOs%2FgGsC%2Bsukl6hfnV5ipS%2FHeK7pxV2Csv9k%3D&reserved=0
> <
> https://github.com/apache/james-project/blob/master/server/apps/jpa-app/pom.xml#L268
> >
> >
> > For my development, after the command `maven install` the image tar will
> be
> > created at server/apps/jpa-app/target/jib-image.tar. After that `docker
> > load -i jib-image.tar` to get the image. If you want to build image
> > `apache/james: jpa-3.7.2`, you can `git checkout james-project-3.7.2` and
> > then run the command maven build.
> >
> > Cheer,
> > Tung, Tran Van
> >
> > On Tue, Nov 7, 2023 at 8:33 PM Garrett Singletary <
> [email protected]>
> > wrote:
> >
> >> I am working with James for the first time and am attempting to build my
> >> own image (single node with some custom mailets) using the jpa-app
> compose
> >> file<
> >>
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fjames-project%2Fblob%2F3.8.x%2Fserver%2Fapps%2Fjpa-app%2Fdocker-compose.yml&data=05%7C01%7Cmgryzykhin%40concord.net%7Ca9764562aa5a47e94b2a08dbe00af1cf%7C7674c0a1b7aa4472babee8c09210b014%7C1%7C0%7C638350109849487084%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pX%2BKWqhxMTEQUQ7EKl1UVryLaH4U2T2uw4shIbVwYLM%3D&reserved=0
> ><
> https://github.com/apache/james-project/blob/3.8.x/server/apps/jpa-app/docker-compose.yml
> >
> >> in 3.8 as a reference. The compose file references the
> >> apache/james:jpa-latest as a base image but I am unable to tie this
> image
> >> tag back to a tag in GitHub nor find a Dockerfile to see how it was
> built.
> >> I see tags such as jpa-3.7.2 but again no explicit tie to a git tag,
> just a
> >> suggestive image tag name (even though I assume this image was built
> from
> >> the james-project-3.7.2 branch).
> >>
> >> How can I know which git tag jpa-latest was built from?
> >> How can I know explicitly which git tag jpa-3.*.* was built from?
> >> Am I able to see the Dockerfile for jpa-latest (this would be really
> >> helpful if Iwanted to compile from src and create a custom image)?
> >>
> >> Thanks in advance for any help.
> >>
> >>
> >> Garrett Singletary
> >>
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>