I'm wondering if there is a up-to-date docker image for the Ignite web console?
When I pull "docker pull apacheignite/web-console-standalone" I only get an outdated version that isn't compatible with current web agent.
Or is the Dockerfile available so I can build the image myself without starting from the ground?
Maybe there is even a Dockerfile that puts webagent and console in one?
Thanks for any help!
#dontequila.
apacheignite/web-console-standalone will be updated soon.
You can also build docker by yourself:
Checkout Apache Ignite master: Ignite Git: https://git-wip-us.apache.org/repos/asf/ignite
cd modules/web-console/docker/standalone/
./build.sh (you may need sudo).
Related
I'm attempting to use my WSL2 docker containers with VS Code, though I now regret this. I attempted to follow these directions to get everything installed and configured correctly.
After installing Docker Desktop, my previous containers and images are not shown with docker ls and docker images when run from WSL2. However, there are still many GB of data under /var/lib/docker. Is there some way to attempt to recover this?
I have to build and push docker image via gitlab-ci. I have gone through the official document.
https://docs.gitlab.com/ee/ci/docker/using_docker_build.html
I want to adopt shell method but my issue is I already had a working gitrunner on my server machine. So what the procedure for it. If I tried to re-register the git runner on the same machine. will it impact the old one?
Thanks in advance.
Assuming that you installed gitlab-runner as a system service and not inside a container, you can easily register another shell runner on your server using the command gitlab-ci-multi-runner register.
This is indirectly confirmed by the advanced configuration documentation, which states that the config.toml of the gitlab-runner service may contain multiple [[runner]] sections.
Note: To allow the shell runner to build docker images, you will need to add the gitlab-runner user to the docker group, e.g.:
sudo gpasswd --add gitlab-runner docker
I am running Docker with Linux containers. When I try to do a Redis pull I get "docker: no matching manifest for windows/amd64 in the manifest list entries." I have seen many tutorials showing redis running on docker windows. Has something changed with later versions of redis which means that it no longer works with docker on Windows?
start dockerd.exe with the --experimental flag and your problem will be solved.
easy find on google:
https://github.com/docker/for-win/issues/1100
https://blog.docker.com/2017/09/preview-linux-containers-on-windows/
I am running self-hosted GitLab CE with a GitLab-runner and a Docker executor. I want to build a binary for AWS Lambda, so I'm using the amazonlinux:latest image for my Docker executor.
Of course, not all packages that I need for building are available in the base amazonlinux image, so I install them via yum. Unfortunately, cmake is not available for Amazon Linux, so I build it from source.
At the moment, this takes place every time the pipeline runs, which is not optimal because cmake takes a relatively long time to build (compared to the binary I actually want to build).
My general question is: is there a clean and reproducible way to prepare an image for building, which is then used as base image for GitLab CI? Since I'm relatively new to Docker and friends, is the correct way to go to create an image locally on the runner host and use that in my gitlab-ci.yml? Or should I put it in a registry (probably even GitLab's own container registry?)
Yes there is.
Nothing is stopping you from creating an image through a Dockerfile that does all the yum installs and then pushes the image you build to a (private) Docker registry. Look at it as 'extending' the Amazon image and save it for future usage.
Since I don't expect it to be to exiting (it will not yet contain any application code) you can also store it for free on Docker Hub.
Custom image
So an example Dockerfile:
FROM amazonlinux:latest
RUN yum install <packages>
RUN <commands for cmake>
Then you build your custom amazonlinux-custom image with:
docker build -t mydockerhubuser/amazonlinux-custom:latest .
And push it to Docker Hub (after docker login):
docker push mydockerhubuser/amazonlinux-custom:latest
Gitlab CI usage
In your .gitlab-ci.yml you replace the image: amazonlinux:latest part that defines your job image with image: mydockerhubuser/amazonlinux-custom:latest so you don't have to install all your deps.
Note
Amazon will often rebuild its amazonlinux:latest image and push it to Docker Hub. Using a custom image based on theirs you will have to take in account the following:
You will need to rebuild your image often too, to stay up to date with patches etc.
It may be smarter to use e.g. a fixed version like FROM: amazonlinux:2017.09 to avoid major version changes you don't expect.
I have a Ubuntu 14.04 which run an app supported by Docker (version 17.05.0-ce, build 89658be) and docker-compose (version 1.16.1, build 6d1ac21). One of this dockers contains an Apache which is restating in a loop.
Is there a way to fix this without losing dockers customizations?
I re-created all dockers with
docker-compose up --force-recreate
I didn't lose anything and everything is working now.