Im trying to build a docker image of Wso2 CEP on a linux VM.
I failing in the ./build.sh script and I get the following error meassage
Docker version should be equal to or greater than 1.10.0 to build WSO2 Docker images. Found 17.03.0-ce
How can I solve the docker version issue?
thank you
The docker version validating logic used in scripts are not compatible with latest docker version.
You can comment the following line in common/scripts/docker-build.sh file to skip the validation.
# validateDockerVersion "${docker_version}" "${min_required_docker_version}"
Related
I am able to run my mi dashboard, (i'm using v4.0.1.17 as it allows me to replace the default H2 database), successfully on Windows. I now want to create a docker image for the same version, but I cannot find it's release in the official GitHub repositories. I tried vainly to build an image for provided version 4.0.1.2 and then replaced the zipped directory with my own 4.0.1.17 one, but it didn't work. Any suggestions would be welcome. Thanks.
You can get the updated docker image for MI Dashboard from the WSO2 Private Docker registry. The page wso2mi-dashboard contains a list of all the docker images released with the update tag.
In your case to pull the v4.0.1.17 you can use the following command,
docker pull docker.wso2.com/wso2mi-dashboard:4.0.1.17
Note that you need to log in to docker.wso2.com with the WSO2 subscription credentials before pulling the image
docker login docker.wso2.com
Description:
I build the APIM from this commit and deploy the product on the VMs.
I configured APIM using Documents 1 and 2
Then start the traffic-manager, key-manager, and publisher without any error.
But when I tried to log in to example.com/publisher, I experienced some errors.
Like below:
logs.txt
After getting these errors, I checked the service providers section and saw that the apim_publisher application was created but OAuth keys didn't exist.
Then I checked the consumer_key and consumer_secret's value on the AM_SYSTEM_APPS table in apim_db database, and both of them was undefined
Steps to reproduce:
Build product-apim from this commit
Move wso2am-3.2.0-SNAPSHOT to 5 VMs.
Run the below command for profile optimization for each node.
sh bin/profileSetup.sh -Dprofile=$PROFILE_NAME
Run components in the following order:
sh wso2am-3.2.0-tm/bin/wso2server.sh -Dprofile=traffic-manager
sh wso2am-3.2.0-km/bin/wso2server.sh -Dprofile=api-key-manager
sh wso2am-3.2.0-pub/bin/wso2server.sh -Dprofile=api-publisher
Open the publisher page
Affected Product Version:
APIM 3.2.0 (MariaDB)
Environment details (with versions):
OS: Ubuntu 18.04
Client: Ubuntu 20.04
I have created a standard Windows cluster in AWS Elastic Container Services (ECS) and am trying to deploy an ASP.Net docker image (microsoft/aspnet:4.7.1-windowsservercore-1709) to it and get the following error
Status reason CannotPullContainerError: a Windows version
10.0.16299-based image is incompatible with a 10.0.14393 host
My application is a ASP.Net WebAPI application using .Net Framework 4.6.1.
My docker file is
FROM microsoft/aspnet:4.7.1-windowsservercore-1709
ARG source
WORKDIR /inetpub/wwwroot
COPY ${source:-obj/Docker/publish} .
Can anyone suggest what image I could deploy?
Thanks
Change your FROM to aspnet:4.7.1-windowsservercore-ltsc2016 and it should resolve your issue. Keep in mind the image size for this tag is considerably larger than 1709.
We also got the following message when using AWS ECS:
CannotPullContainerError: a Windows version 10.0.16299-based image is incompatible with a 10.0.14393 host
After a lot of trial and error we found that we were using .NetCore SDK 2.2 and AWS ECS wants 2.1. The developer made changes in Visual Studio 2017 and to the Dockerfile to reference 2.1 instead of 2.2. Once that was done ECS was able to consume it and we had a running state.
Unfortunately the error was not as descriptive and we went down the rabbit hole before discovering what really was our problem.
I'm working on a project that I haven't touched in about 4 months. Before everything on the deploy was working fine, but now I'm getting an error when trying to deploy an update.
Failed to pull Docker image amazon/aws-eb-python:3.4.2-onbuild-3.5.1: Pulling repository amazon/aws-eb-python time="2016-01-17T01:40:45Z" level="fatal" msg="Could not reach any registry endpoint" . Check snapshot logs for details. Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/03build.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
In the eb-activity log, it further states [CMD-AppDeploy/AppDeployStage0/AppDeployPreHook/03build.sh] : Activity execution failed, because: Pulling repository amazon/aws-eb-python before repeating what was shown in the UI.
The original was using a Preconfigured Docker 64bit Debian jessie v1.3.1 running Python 3.4. I've tried upgrading to the latest, which is version 2.0.6, but it never completes (don't need to get into specifics of that error, separate issue and I'd like to stay on 1.3.1 if possible). I've also tried upgrading to the latest 1.x but it has the same result of upgrading to 2.0.6.
Any ideas, or anything else I should be looking for clues?
Docker Hub has deprecated pulls from Docker clients on 1.5 and earlier. Make sure that your docker client version is at least above 1.5. See https://blog.docker.com/2015/10/docker-hub-deprecation-1-5/ for more information.
I downloaded zip file in wso2 and i extracted the file as /home/Downloads/jacksphere/LatestVersion/wso2bam-2.3.0/bin and run at server side,but it is not showing some errors,is there any pre requisites to install the product any one help us and explain the procedure how to run the bam server..
The only pre-requisite required for running WSO2 BAM is JDK1.6 or higher. For further information please checkout the documentation WSO2 BAM Documentation
If you have downloaded the zip file then you can simply extract it and start the server by moving to bin directory and executing the command ./wso2server.sh (in Linux) or wso2server.bat (in Windows).
You also need to install JDK 1.6 or 1.7. Apache Ant and Curl will also be required to run samples.
If you are working with Windows you need to install Cygwin.
You can further refer to the BAM documents in [1] about installing the product.
[1] http://docs.wso2.org/wiki/display/BAM230/Installing+the+Product