I am running a Jenkins job, inside a docker container, this job requires doxygen but im getting an error saying – I have doxygen installed in my Docker image, but the path is – Inside my docker image, I want to connect this old path – /opt/fc4-usr-local/bin/doxygen with new path usr/bin/doxygen So whenever my job looks for doxygen it goes
Tag: docker-compose
Incorrect permissions for file with docker compose volume? 13: Permission denied
I have the following docker_compose.yaml: When I run via docker compose I get the following error: So to investigate I re-ran just the nginx container: ssh’d in and I see: I consulted the following Q and others and they seem to suggest to just restart the docker service, so I did and I still get ? permissions upon re running.
Couldn’t connect to Docker daemon
I am new in Docker and CICD I am using a vps with Ubuntu 18.04. The docker of the project runs locally and works fine. I don’t quite understand why the server is trying to find the docker on http, not on tcp. override.conf docker service status daemon.json gitlab-ci.yml Error Answer Set the DOCKER_HOST variable. When using the docker:dind service,
Using wait-for-it.sh to wait on an endpoint with a slash
Background: I have a project that runs a docker image (in production it will run in knative, but for testing, docker/docker compose is a good first step), and as part of my CI/CD pipeline, I would like to run acceptance tests against the image. I have the image configured to run in docker, and the (cucumber) acceptance tests run as
Docker overlay2 resource is busy
I need some help with docker! 😀 When I have to deploy my application, sometimes I have this error OR This is my docker info output: Everytime that the resource is busy error appears, I move the HASH’s directory in /var/lib/docker/(containers OR overlay2) to HASH_old directory and retry to deploy the application, used to work, but now the no such
Start docker containers on linux system startup from user directory
I’ve downloaded two docker containers and already configure them. So, now all I want is to start them on system startup. They are in a path like /home/user/docker-mailserver /home/user/docker-webserver Hosted on a Ubuntu 18.04.01 (x64) On boot those docker containers are not running. On login, those docker containers are starting. I already tried to do something like docker run -it
Geting the private ip for the docker network from within the container to configure xdebug remote_host
So using docker and docker-compose I like to provide tools built into the containers so that other people in the development team don’t have to struggle with setting up bits and bobs. In this specific case I’m having issues configuring xdebug. It works absolutely fine using connect back when debugging from a browser. But trying to get xdebug working through
docker compose: Error while loading shared libraries: libz.so.1: failed to map segment from shared object: Operation not permitted
After installing docker and docker-compose on: When executing: It returns: Error while loading shared libraries: libz.so.1: failed to map segment from shared object: Operation not permitted It should return: Installation from docker-compose is this Answer Got it solved by re-mounting the /tmp to give the volume permission to execute (it was accessible with read-only). So this solved:
How to configure supervisor in docker correctly
I have a working laravel environment using docker. my projects has multiple services in different container such as redis, mongodb, mysqldb and nodejs. I want to use supervisor on my project to interact with redis for the queues and php to run the job. I have done some testing and research but I really can’t make it work. so here
My container isn’t finding the package.json to execute npm install on docker-compose
I’m trying to deploy an application using docker-compose and the app is in a folder in the host machine (in the same dir that the docker-compose file). I’m runnig the command docker-compose up -d, however, it seems that the volume isn’t mounting because when the command npm install is executed the following message is displayed: After that my container is