"Getting Started" with JAMES using Docker
I was preparing to do a trial run at getting James up and running on an AWS EC2 instance. I went to the James home page and saw there is a 1-line command to download and install it. However, to use that one line there is apparently an assumption of a full understanding of Docker and a pre-existing installation of Docker. Docker isn't automatically installed with Amazon Linux in an EC2. I was able to install it with yum. But when I entered the command from the JAMES getting started page, this is what I got: [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.0 Unable to find image 'linagora/james-jpa-sample:3.3.0' locally docker: Error response from daemon: manifest for linagora/james-jpa-sample:3.3.0 not found. See 'docker run --help'. Since there's no url to download james, I assume that the manifest that it is saying that it can't find contains all of that useful info. I know nothing about how Docker works. Where would I find the missing manifest, and if it was expected to automatically come with Docker as implied with the "1-line-download-install" statement, what did I do wrong? Thx Jerry - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Re: "Getting Started" with JAMES using Docker
Hi Jerry, I'll try to be brief and not to come into many details of how Docker is working. For that, I suggest that you go through some video materials and/or to find some really extensive documentation on Internet (blogs, posts, Docker documentation, books, etc.) In the meantime, I'll try to explain what happened in your case. Obviously you've installed Docker correctly as we can see from command response. There are actually two concepts in Docker that you have to distinguish: Docker Image and Docker Container. Docker Container is "running version" of Docker Image. When you stated: [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.0 It actually means that it will try to run Docker Container, listening on host ports 25 and 143, and Container should be of a Docker Image "linagora/james-jpa-sample:3.3.0". That image, "linagora/james-jpa-sample:3.3.0", should be availabe either locally or placed somewhere on Internet, so Docker can access it and grab it. For this kind of Docker Image store, usually people use Docker Hub (https://hub.docker.com/), but there are also other Docker Repositories (private or public). As you don't have it locally, that Docker Image ("linagora/james-jpa-sample:3.3.0"), therefore you've got that information in reponse: "Unable to find image 'linagora/james-jpa-sample:3.3.0' locally". At that moment, Docker Engine will try to grab that image from Docker Hub. But unfortunately, I don't see that 3.3.0 version of that image exists. You can go to URL (https://hub.docker.com/r/linagora/james-jpa-sample/tags) for yourself and make sure that it doesn't exists. I don't know how did you get that 3.3.0, maybe it is in some outdated documentation, but I suggest that you try either with latest tag (so the command would be docker run -p "25:25" -p "143:143" linagora/james-jpa-sample) or if you really have some reasons for 3.3.X then I would try with docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.X Let's try that and then just reply to this thread. Than You On Thu, Aug 29, 2019 at 5:18 AM Jerry Malcolm wrote: > I was preparing to do a trial run at getting James up and running on an > AWS EC2 instance. I went to the James home page and saw there is a > 1-line command to download and install it. However, to use that one > line there is apparently an assumption of a full understanding of Docker > and a pre-existing installation of Docker. Docker isn't automatically > installed with Amazon Linux in an EC2. I was able to install it with > yum. But when I entered the command from the JAMES getting started > page, this is what I got: > > [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" > linagora/james-jpa-sample:3.3.0 > Unable to find image 'linagora/james-jpa-sample:3.3.0' locally > docker: Error response from daemon: manifest for > linagora/james-jpa-sample:3.3.0 not found. > See 'docker run --help'. > > Since there's no url to download james, I assume that the manifest that > it is saying that it can't find contains all of that useful info. I > know nothing about how Docker works. Where would I find the missing > manifest, and if it was expected to automatically come with Docker as > implied with the "1-line-download-install" statement, what did I do wrong? > > Thx > > Jerry > > > - > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > > -- Aleksandar dipl. ing. Stoisavljevic Java Software Architect E-mail:stal...@gmail.com SkypeId: staleks_ns LinkedIn: http://www.linkedin.com/in/astoisavljevic Web: http://staleks.github.io Mail: Branislava Nusica 10, 21000 Novi Sad, Serbia
Re: "Getting Started" with JAMES using Docker
Thanks for the detailed info. I have no real desire to get into Docker at this point (likely will at a later date). I was just enticed by the statement on the James home page: (http://james.apache.org/index.html) that says I can download and install James in one statement: *= * *STEPS YOU HAVE TO FOLLOW:* Pull and run the James image with the following single command: |docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.0| Then, connect this image with for instance, Thunderbird. I just did what it said. I'll try dropping off the 3.3.0. But I feel like we're just shooting in the dark trying to guess at the package name docker is looking for. Is there a way to list the package names that docker is aware of? Thx Jerry On 8/29/2019 2:53 AM, Aleksandar Stoisavljevic wrote: Hi Jerry, I'll try to be brief and not to come into many details of how Docker is working. For that, I suggest that you go through some video materials and/or to find some really extensive documentation on Internet (blogs, posts, Docker documentation, books, etc.) In the meantime, I'll try to explain what happened in your case. Obviously you've installed Docker correctly as we can see from command response. There are actually two concepts in Docker that you have to distinguish: Docker Image and Docker Container. Docker Container is "running version" of Docker Image. When you stated: [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.0 It actually means that it will try to run Docker Container, listening on host ports 25 and 143, and Container should be of a Docker Image "linagora/james-jpa-sample:3.3.0". That image, "linagora/james-jpa-sample:3.3.0", should be availabe either locally or placed somewhere on Internet, so Docker can access it and grab it. For this kind of Docker Image store, usually people use Docker Hub (https://hub.docker.com/), but there are also other Docker Repositories (private or public). As you don't have it locally, that Docker Image ("linagora/james-jpa-sample:3.3.0"), therefore you've got that information in reponse: "Unable to find image 'linagora/james-jpa-sample:3.3.0' locally". At that moment, Docker Engine will try to grab that image from Docker Hub. But unfortunately, I don't see that 3.3.0 version of that image exists. You can go to URL (https://hub.docker.com/r/linagora/james-jpa-sample/tags) for yourself and make sure that it doesn't exists. I don't know how did you get that 3.3.0, maybe it is in some outdated documentation, but I suggest that you try either with latest tag (so the command would be docker run -p "25:25" -p "143:143" linagora/james-jpa-sample) or if you really have some reasons for 3.3.X then I would try with docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.X Let's try that and then just reply to this thread. Than You On Thu, Aug 29, 2019 at 5:18 AM Jerry Malcolm wrote: I was preparing to do a trial run at getting James up and running on an AWS EC2 instance. I went to the James home page and saw there is a 1-line command to download and install it. However, to use that one line there is apparently an assumption of a full understanding of Docker and a pre-existing installation of Docker. Docker isn't automatically installed with Amazon Linux in an EC2. I was able to install it with yum. But when I entered the command from the JAMES getting started page, this is what I got: [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.0 Unable to find image 'linagora/james-jpa-sample:3.3.0' locally docker: Error response from daemon: manifest for linagora/james-jpa-sample:3.3.0 not found. See 'docker run --help'. Since there's no url to download james, I assume that the manifest that it is saying that it can't find contains all of that useful info. I know nothing about how Docker works. Where would I find the missing manifest, and if it was expected to automatically come with Docker as implied with the "1-line-download-install" statement, what did I do wrong? Thx Jerry - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Re: "Getting Started" with JAMES using Docker
Hi Jerry, I understand your concern, don't get me wrong, I'm not connected to James project. Just a subscriber to this list as you are. However, I have experience in Java, and Docker lately so that was my reason to jump in and to try to help you. As I've assumed, probably outdated documentation. Here you can find list of linagora Docker images: https://hub.docker.com/r/linagora/james-jpa-sample/tags I see now that there is 3.3.0 (built just 6 hrs ago). Maybe you can try it now? Thank You On Thu, Aug 29, 2019 at 4:38 PM Jerry Malcolm wrote: > Thanks for the detailed info. I have no real desire to get into Docker > at this point (likely will at a later date). I was just enticed by the > statement on the James home page: (http://james.apache.org/index.html) > that says I can download and install James in one statement: > > *= > * > > *STEPS YOU HAVE TO FOLLOW:* > Pull and run the James image with the following single command: > > |docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.0| > > Then, connect this image with for instance, Thunderbird. > > > > I just did what it said. I'll try dropping off the 3.3.0. But I feel > like we're just shooting in the dark trying to guess at the package name > docker is looking for. Is there a way to list the package names that > docker is aware of? > > Thx > > Jerry > > On 8/29/2019 2:53 AM, Aleksandar Stoisavljevic wrote: > > Hi Jerry, > > > > I'll try to be brief and not to come into many details of how Docker is > > working. > > For that, I suggest that you go through some video materials and/or to > find > > some > > really extensive documentation on Internet (blogs, posts, Docker > > documentation, books, etc.) > > > > In the meantime, I'll try to explain what happened in your case. > > > > Obviously you've installed Docker correctly as we can see from command > > response. > > > > There are actually two concepts in Docker that you have to distinguish: > > Docker Image and > > Docker Container. > > Docker Container is "running version" of Docker Image. > > > > When you stated: > > > > [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" > > linagora/james-jpa-sample:3.3.0 > > > > It actually means that it will try to run Docker Container, listening on > > host ports 25 and 143, and Container should > > be of a Docker Image "linagora/james-jpa-sample:3.3.0". > > > > That image, "linagora/james-jpa-sample:3.3.0", should be availabe either > > locally or placed somewhere on Internet, so > > Docker can access it and grab it. For this kind of Docker Image store, > > usually people use Docker Hub (https://hub.docker.com/), > > but there are also other Docker Repositories (private or public). > > > > As you don't have it locally, that Docker Image > > ("linagora/james-jpa-sample:3.3.0"), therefore you've got that > information > > in reponse: > > "Unable to find image 'linagora/james-jpa-sample:3.3.0' locally". > > > > At that moment, Docker Engine will try to grab that image from Docker > Hub. > > > > But unfortunately, I don't see that 3.3.0 version of that image exists. > > You can go to URL ( > https://hub.docker.com/r/linagora/james-jpa-sample/tags) > > for yourself and make sure that it doesn't exists. > > > > I don't know how did you get that 3.3.0, maybe it is in some outdated > > documentation, but I suggest that you try either with latest tag > > (so the command would be docker run -p "25:25" -p "143:143" > > linagora/james-jpa-sample) or if you really have some reasons for 3.3.X > > then I would try with docker run -p "25:25" -p "143:143" > > linagora/james-jpa-sample:3.3.X > > > > Let's try that and then just reply to this thread. > > > > > > Than You > > > > > > > > On Thu, Aug 29, 2019 at 5:18 AM Jerry Malcolm > > wrote: > > > >> I was preparing to do a trial run at getting James up and running on an > >> AWS EC2 instance. I went to the James home page and saw there is a > >> 1-line command to download and install it. However, to use that one > >> line there is apparently an assumption of a full understanding of Docker > >> and a pre-existing installation of Docker. Docker isn't automatically > >> installed with Amazon Linux in an EC2. I was able to install it with > >> yum. But when I entered the command from the JAMES getting started > >> page, this is what I got: > >> > >> [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" > >> linagora/james-jpa-sample:3.3.0 > >> Unable to find image 'linagora/james-jpa-sample:3.3.0' locally > >> docker: Error response from daemon: manifest for > >> linagora/james-jpa-sample:3.3.0 not found. > >> See 'docker run --help'. > >> > >> Since there's no url to download james, I assume that the manifest that > >> it is saying that it can't find contains all of that useful info. I > >> know nothing about how Docker works. Where would I find the missing > >> manifest, and if it was expected to automatically come with Docker as > >> implied with the "1-line-down
Re: "Getting Started" with JAMES using Docker
Hi, Aleksanda, I really appreciate your information. I believe that someone realized the image wasn't there and quietly got it posted overnight. When I reran the command it worked, at least somewhat. Just an unsolicited opinion for the James folks... I'm not sure that one line command as the first thing a new user will see is quite ready for prime-time. As I mentioned in my first post yesterday, there is an implied assumption that the user understands docker and has it installed. Nothing against docker. But it has not yet attained ubiquity. My guess is a lot of new James users will have no idea what it is or where to get it, either for Linux or Windows. And if that's the case, there's no alternative pointer on that home page for non-docker install. Next, the docker install failed for me because port 25 was already in use since aws ec2 Linux automatically installs sendmail and starts it up. Maybe all new James users will implicitly understand what that error means and how to fix it. Finally, docker got to the point of creating the dummy user ids and locked up. Had to kill my puTTY session. No idea how to try to start/stop the james service and see how much, if any of it, is installed and runable. I'm not trying to be negative. That one line install is great if it really works for the majority. But if a user (even a veteran of JAMES for ~15 years like me) has the problems I've encountered, I would strongly suggest a detailed followup page to go to when the one line install crashes and burns. If I wasn't a seasoned user of James, and rather a first-timer with this supposedly 'super easy' experience to get it up and running, I might decide to go another direction for my MTA needs. I think we can head that off with a pointer to more info and what to do if things don't go right on that one-line install. Thx Jerry On 8/29/2019 2:53 AM, Aleksandar Stoisavljevic wrote: Hi Jerry, I'll try to be brief and not to come into many details of how Docker is working. For that, I suggest that you go through some video materials and/or to find some really extensive documentation on Internet (blogs, posts, Docker documentation, books, etc.) In the meantime, I'll try to explain what happened in your case. Obviously you've installed Docker correctly as we can see from command response. There are actually two concepts in Docker that you have to distinguish: Docker Image and Docker Container. Docker Container is "running version" of Docker Image. When you stated: [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.0 It actually means that it will try to run Docker Container, listening on host ports 25 and 143, and Container should be of a Docker Image "linagora/james-jpa-sample:3.3.0". That image, "linagora/james-jpa-sample:3.3.0", should be availabe either locally or placed somewhere on Internet, so Docker can access it and grab it. For this kind of Docker Image store, usually people use Docker Hub (https://hub.docker.com/), but there are also other Docker Repositories (private or public). As you don't have it locally, that Docker Image ("linagora/james-jpa-sample:3.3.0"), therefore you've got that information in reponse: "Unable to find image 'linagora/james-jpa-sample:3.3.0' locally". At that moment, Docker Engine will try to grab that image from Docker Hub. But unfortunately, I don't see that 3.3.0 version of that image exists. You can go to URL (https://hub.docker.com/r/linagora/james-jpa-sample/tags) for yourself and make sure that it doesn't exists. I don't know how did you get that 3.3.0, maybe it is in some outdated documentation, but I suggest that you try either with latest tag (so the command would be docker run -p "25:25" -p "143:143" linagora/james-jpa-sample) or if you really have some reasons for 3.3.X then I would try with docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.X Let's try that and then just reply to this thread. Than You On Thu, Aug 29, 2019 at 5:18 AM Jerry Malcolm wrote: I was preparing to do a trial run at getting James up and running on an AWS EC2 instance. I went to the James home page and saw there is a 1-line command to download and install it. However, to use that one line there is apparently an assumption of a full understanding of Docker and a pre-existing installation of Docker. Docker isn't automatically installed with Amazon Linux in an EC2. I was able to install it with yum. But when I entered the command from the JAMES getting started page, this is what I got: [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.0 Unable to find image 'linagora/james-jpa-sample:3.3.0' locally docker: Error response from daemon: manifest for linagora/james-jpa-sample:3.3.0 not found. See 'docker run --help'. Since there's no url to download james, I assume that the manifest that it is saying that it can't find contains all
Re: "Getting Started" with JAMES using Docker
Hi Jerry, Yes thanks to your report, the image had been updated. Thanks! > Just an unsolicited opinion for the James folks... >> there is an implied assumption that the user understands docker and has it installed. Nothing against docker. But it has not yet attained ubiquity. Well, thanks for the feedback. IMO you see it the wrong way. IF you have/are-familiar-with docker you can get a one line try - which is awesome. If you do not have it, you can follow one of the many non-docker tutorials. CF: http://james.apache.org/server/install.html Regarding "windows support" we are actively looking for some contributors... Most of us don't have a license... I'm not going to answer docker sysadmin related issues here. Maybe the key output would be to enrich the **Get started with James** section in order to also link "non-docker install options". Would you agree with such a proposal? Thanks again for your feedback, it's really helpful. Best regards, Benoit On 30/08/2019 11:40, Jerry Malcolm wrote: > Hi, Aleksanda, > > I really appreciate your information. I believe that someone realized > the image wasn't there and quietly got it posted overnight. When I > reran the command it worked, at least somewhat. > > Just an unsolicited opinion for the James folks... I'm not sure that one > line command as the first thing a new user will see is quite ready for > prime-time. As I mentioned in my first post yesterday, there is an > implied assumption that the user understands docker and has it > installed. Nothing against docker. But it has not yet attained > ubiquity. My guess is a lot of new James users will have no idea what > it is or where to get it, either for Linux or Windows. And if that's the > case, there's no alternative pointer on that home page for non-docker > install. Next, the docker install failed for me because port 25 was > already in use since aws ec2 Linux automatically installs sendmail and > starts it up. Maybe all new James users will implicitly understand what > that error means and how to fix it. Finally, docker got to the point of > creating the dummy user ids and locked up. Had to kill my puTTY > session. No idea how to try to start/stop the james service and see how > much, if any of it, is installed and runable. > > I'm not trying to be negative. That one line install is great if it > really works for the majority. But if a user (even a veteran of JAMES > for ~15 years like me) has the problems I've encountered, I would > strongly suggest a detailed followup page to go to when the one line > install crashes and burns. If I wasn't a seasoned user of James, and > rather a first-timer with this supposedly 'super easy' experience to > get it up and running, I might decide to go another direction for my MTA > needs. I think we can head that off with a pointer to more info and > what to do if things don't go right on that one-line install. > > Thx > > Jerry > > > On 8/29/2019 2:53 AM, Aleksandar Stoisavljevic wrote: >> Hi Jerry, >> >> I'll try to be brief and not to come into many details of how Docker is >> working. >> For that, I suggest that you go through some video materials and/or to >> find >> some >> really extensive documentation on Internet (blogs, posts, Docker >> documentation, books, etc.) >> >> In the meantime, I'll try to explain what happened in your case. >> >> Obviously you've installed Docker correctly as we can see from command >> response. >> >> There are actually two concepts in Docker that you have to distinguish: >> Docker Image and >> Docker Container. >> Docker Container is "running version" of Docker Image. >> >> When you stated: >> >> [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" >> linagora/james-jpa-sample:3.3.0 >> >> It actually means that it will try to run Docker Container, listening on >> host ports 25 and 143, and Container should >> be of a Docker Image "linagora/james-jpa-sample:3.3.0". >> >> That image, "linagora/james-jpa-sample:3.3.0", should be availabe either >> locally or placed somewhere on Internet, so >> Docker can access it and grab it. For this kind of Docker Image store, >> usually people use Docker Hub (https://hub.docker.com/), >> but there are also other Docker Repositories (private or public). >> >> As you don't have it locally, that Docker Image >> ("linagora/james-jpa-sample:3.3.0"), therefore you've got that >> information >> in reponse: >> "Unable to find image 'linagora/james-jpa-sample:3.3.0' locally". >> >> At that moment, Docker Engine will try to grab that image from Docker >> Hub. >> >> But unfortunately, I don't see that 3.3.0 version of that image exists. >> You can go to URL >> (https://hub.docker.com/r/linagora/james-jpa-sample/tags) >> for yourself and make sure that it doesn't exists. >> >> I don't know how did you get that 3.3.0, maybe it is in some outdated >> documentation, but I suggest that you try either with latest tag >> (so the command would be docker run -p "25:25"
Re: "Getting Started" with JAMES using Docker
Hi Tellier, Thanks for the response. You're suggestion is a perfect solution. Just add the option to the quick start: if you know docker, do this way. If you want do it the traditional way, here's the steps. Thanks. Jerry On 8/30/2019 12:04 AM, Tellier Benoit wrote: Hi Jerry, Yes thanks to your report, the image had been updated. Thanks! Just an unsolicited opinion for the James folks... there is an implied assumption that the user understands docker and has it installed. Nothing against docker. But it has not yet attained ubiquity. Well, thanks for the feedback. IMO you see it the wrong way. IF you have/are-familiar-with docker you can get a one line try - which is awesome. If you do not have it, you can follow one of the many non-docker tutorials. CF: http://james.apache.org/server/install.html Regarding "windows support" we are actively looking for some contributors... Most of us don't have a license... I'm not going to answer docker sysadmin related issues here. Maybe the key output would be to enrich the **Get started with James** section in order to also link "non-docker install options". Would you agree with such a proposal? Thanks again for your feedback, it's really helpful. Best regards, Benoit On 30/08/2019 11:40, Jerry Malcolm wrote: Hi, Aleksanda, I really appreciate your information. I believe that someone realized the image wasn't there and quietly got it posted overnight. When I reran the command it worked, at least somewhat. Just an unsolicited opinion for the James folks... I'm not sure that one line command as the first thing a new user will see is quite ready for prime-time. As I mentioned in my first post yesterday, there is an implied assumption that the user understands docker and has it installed. Nothing against docker. But it has not yet attained ubiquity. My guess is a lot of new James users will have no idea what it is or where to get it, either for Linux or Windows. And if that's the case, there's no alternative pointer on that home page for non-docker install. Next, the docker install failed for me because port 25 was already in use since aws ec2 Linux automatically installs sendmail and starts it up. Maybe all new James users will implicitly understand what that error means and how to fix it. Finally, docker got to the point of creating the dummy user ids and locked up. Had to kill my puTTY session. No idea how to try to start/stop the james service and see how much, if any of it, is installed and runable. I'm not trying to be negative. That one line install is great if it really works for the majority. But if a user (even a veteran of JAMES for ~15 years like me) has the problems I've encountered, I would strongly suggest a detailed followup page to go to when the one line install crashes and burns. If I wasn't a seasoned user of James, and rather a first-timer with this supposedly 'super easy' experience to get it up and running, I might decide to go another direction for my MTA needs. I think we can head that off with a pointer to more info and what to do if things don't go right on that one-line install. Thx Jerry On 8/29/2019 2:53 AM, Aleksandar Stoisavljevic wrote: Hi Jerry, I'll try to be brief and not to come into many details of how Docker is working. For that, I suggest that you go through some video materials and/or to find some really extensive documentation on Internet (blogs, posts, Docker documentation, books, etc.) In the meantime, I'll try to explain what happened in your case. Obviously you've installed Docker correctly as we can see from command response. There are actually two concepts in Docker that you have to distinguish: Docker Image and Docker Container. Docker Container is "running version" of Docker Image. When you stated: [ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143" linagora/james-jpa-sample:3.3.0 It actually means that it will try to run Docker Container, listening on host ports 25 and 143, and Container should be of a Docker Image "linagora/james-jpa-sample:3.3.0". That image, "linagora/james-jpa-sample:3.3.0", should be availabe either locally or placed somewhere on Internet, so Docker can access it and grab it. For this kind of Docker Image store, usually people use Docker Hub (https://hub.docker.com/), but there are also other Docker Repositories (private or public). As you don't have it locally, that Docker Image ("linagora/james-jpa-sample:3.3.0"), therefore you've got that information in reponse: "Unable to find image 'linagora/james-jpa-sample:3.3.0' locally". At that moment, Docker Engine will try to grab that image from Docker Hub. But unfortunately, I don't see that 3.3.0 version of that image exists. You can go to URL (https://hub.docker.com/r/linagora/james-jpa-sample/tags) for yourself and make sure that it doesn't exists. I don't know how did you get that 3.3.0, maybe it is in some outdated documentation, but I suggest that you try either with