This response is for
Kernel: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524
Architecture: aarch64 aarch64 aarch64 GNU/Linux
I had the same issue when issuing commands to a cluster in swarm mode.
Running docker info would result in Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Running sudo systemctl ...
One could use A2D to bake an app into a docker image while taking certain things into account, e.g. non-root, permissions, location of the app:
docker run -v $PWD:/projectName utrecht/a2d:1.0.0 \
-projectName someProjectName -dockerfile /projectName/Dockerfile
FROM golang:1.12.4-alpine as builder
COPY . ./someProjectName/
docker-compose up will remove containers when:
The service name is the same, but has a change, in which case the old container is replaced with the new state of the service
You include the --remove-orphans option when running docker-compose
Otherwise, if you change the name of the service, and do not specify --remove-orphans, you will see "orphaned" ...
You are using docker wrongly in this case IMHO and I have a serious doubt that your docker exec command is targeting the correct container because, from what I see (and my very limited knowledge of sbt/scala), it should be dead by the time the jar is published. Let me explain.
sbt publishLocal is not a long living command. It will exit when the jar is ...
The base image is buildpack-deps:jessie-scm based on the Dockerfile here. So the linux distro is Debian Jessie.
The ADD file: ... line shows that the first layer in the image was created by adding some files from outside the image (similar to "COPY" shown in the other layers)
From Dockerfile reference:
The ADD instruction copies new files, directories ...
The Docker website doesn't know about your operating system and has no docker installation for you.
Try the one packaged by raspbian:
sudo apt install docker.io
The name is different in some distributions, you can use:
apt-cache search docker
To see if you can find one. If you can't find any, then switch to an older (or newer?) version of Raspbian.
You need to learn a bit more about Debian or Ubuntu. If you look at every single Debian or Ubuntu container that installs things, you will notice, amongst other things:
apt-get update && apt -f install [whatever]
The reason for this is that aptitude doesn't know where to find anything without the "apt update".
See for example https://github.com/...
Don't quote the command you're trying to run, just do:
docker run --rm -it -v ~/Users/mow/Documents/devFolder/testdev:/app testdev_php php ./vendor/bin/phpunit
Your image is looking for a file called "php ./vendor/bin/phpunit" instead of looking for "php" and passing everything else on the line to it.
This is the real reason docker requires all your ...
Not knowing anything about the java appication, but just going on what you can do with docker: The workdir for the parent image is /root. You can try to omit the WORKDIR statement. The build script might be working in the current directory, which would not be /root, but /workdir. Or you can add WORKDIR /root again before CMD.
Also don't forget some basic ...
On Linux, containers live in separate network namespaces, so localhost or 127.0.0.1 on the container is not localhost on the host. I'm not sure about other OSes. You could expose a port to the host like this:
docker run -p 3306:3306 mysql
Then you can access it from any container at the host IP address, which for the default network is 172.17.0.1:3306. You ...
apparently docker needs to be installed on jenkins master in order for jenkins to be able to launch the docker on the server.
After installation of docker (even without the docker daemon running on jenkins master); jenkins was able to launch the docker on my-server.
What you're after is referred to as "Review Apps" by Gitlab and Heroku. It relies on a CI/CD system that runs pipelines on every branch, and exposes the branch name to the build (usually as an environment variable). You can then use the branch name to namespace the resources created by your Infrastructure as Code.
You have mentioned Docker so I will use ...
I suggest you mount your conf file as a volume:
docker run -v nginx.conf:/etc/nginx/nginx.conf ....
This way you can easily change the file outside the container and then just restart the container. If you change your config file inside the container and then you should have to restart nginx to pick-up the changes. At that point your container will stop ...
This seems to be the right idea: https://stackoverflow.com/questions/29328278/installing-jenkins-plugins-to-docker-jenkins/29328489#29328489
so in the Dockerfile you'd just use:
COPY plugins.txt /usr/share/jenkins/plugins.txt
RUN /usr/local/bin/install-plugins.sh < /usr/share/jenkins/plugins.txt
I tried it and it worked for me.
While I'd normally agree with the other answers that Kubernetes is overkill, KubeSail simplifies it as much as possible in order to make it easy to run tasks like yours. There is a free tier that should let you run your job indefinitely. You just need to log in with GitHub, get your Kube config, and then you can use the following:
There's a variety of techniques involved, with no single solution. You will likely want to do several of the following:
First, optimize your image layers for reuse. Put frequently changing steps later in the Dockerfile to increase the chances that early layers are cached from previous builds. A reused layer will show up as more disk space in a docker image ...
One could also use dive
docker run --rm -it \
-v /var/run/docker.sock:/var/run/docker.sock \
wagoodman/dive:latest <dive arguments...>
to get a report about what waste could be removed from a docker image in order to reduce the size.
This volume could be overwriting what you have installed during the RUN npm install stage of the Dockerfile. As far as I can see you're not doing any installation when starting the container, so the contents of the mount are empty. If you remove that mount, the node_modules path will be populated with what was ...
As mentioned in the post/question, it was an issue with volumes, my PC's firewall was blocking the Docker from accessing the drives in my local machine, I reset the credentials in 'Docker for Desktop' app in the shared drives section and everything was back working once again :). Thank you everyone, in fact BMitch was suggesting the same solution, but I was ...
dev packages are typically intended for development and build purposes. They usually contain header files and other resources for providing programmer APIs. For example, python-dev contains C headers for C/C++ applications that integrate python functionalities (which of course isn't necessarily python itself).
The "non-dev" packages provide the actual ...
There is a good practice called multistage build, in which you have one Dockerfile containing various image definitions that depend from one another, this helps you keep all your images updated with the latest changes and copy artifacts from one to another; this also helps reducing the image size if done right.
A simple example is like the following:
This is a glibc dependency issue on Alpine.
This azcopy binary is compatible with Linux distributions that use glibc, GNU's C standard library. Alpine Linux uses a different libc implementation, musl-libc, which is generally not compatible to glibc. When trying to run non-Alpine-built binaries on Alpine, they'll usually fail to link since the glibc shared ...
Use CodeBuild to push the new image. Make sure the task definition is using the "latest" tag. You'll need to force the deployment of the task definition to pick the new image.
Use CodePipeline to update ECS. It will automatically generate a new task definition revision with the new image and deploy it.
Mounted volumes can be used to preserve state between runs, apart from that Docker is stateless by design. To make a local directory available inside the Docker container, you can use the -v option, for example:
docker run -v /path/to/local/dir/:/mountpath/inside/docker ...
But if I understand your question correctly, you are asking for a faster feedback ...
There are options in docker that will retry the startup of a container, restart in version 2 and restart-policy in version 3 (you'd need compatibility mode enabled for the version 3 syntax to work). However, I believe they only work when the issue is from the application inside the container fails, not when there is an issue creating the container like you ...
Managing versions of different services can be tricky. For now I've never found a good HOW TO out there. Like most things you do what suit you the best. Here is a couple of suggestion you could use:
-> Tag docker image with their commit sha:
Pretty easy to do when you are using gitlab this is an already set environment variable that you can uses when ...
why do you want to create a new manager node risking damaging your raft consensus and cie...
I find it way more easier to simply expose the docker socket locally like you where working inside the node but with you windows environment.
To do so simply open an ssh tunnel that expose the /var/run/docker.sock
ssh -M -S ~/.docker.sock \
-fnNT -4 -L ...
No, docker will delete the container when it stops, and there's no update option to change that behavior. You can see this in the help output:
$ docker container update --help
Usage: docker container update [OPTIONS] CONTAINER [CONTAINER...]
Update configuration of one or more containers
--blkio-weight uint16 Block IO (relative ...
Most likely the port is published on the VM and you are trying to connect to your laptop's IP and not seeing it. Newer versions of docker that use xhyve include some networking tricks to publish the port all the way to your laptop, but docker-machine with VirtualBox does not do this.
You can lookup the IP of your VM with docker-machine ls or see it in the ...
The key here is the behavior of AWS AMIs in the context of ECS. By default the AWS ECS Amazon Linux AMI optimized for ECS is in charge of VOLUME management but there's a problem if you copy that AMI and try to launch a new instance, the SECONDARY volume that ECS uses to deploy docker on can go missing.