I write a Dockerfile and docker-compose.yml to build a custom image which combines beakerx and cling, which contents are below. and Some logs of docker-compose build were But When I run docker-compose up -d, I got PermissionError: [Errno 13] Permission denied: ‘/home/beakerx/.local/share’ error. So I drive into the docker image. Why the permission of ~/.local/share was a lot of question
Tag: docker
Why does MSSQL in Docker return “The last operation was terminated because the user pressed CTRL+C” on sql queries?
I’m on Archlinux 64x (4.17.4-1-ARCH) with Docker (version 18.06.0-ce, build 0ffa8257ec). I’m using Microsoft’s MSSQL docker container CU7. Each time I’m trying to enter a query or to run a SQL file I get this warning message: Then when I check in the database with Datagrip, the query hasn’t been executed! Here are my commands : My question is How
Starting container process caused “exec: \”tail -f /dev/null\”: stat tail -f /dev/null: no such file or directory
Because I am trying to keep a container running I specified the “tail -f /dev/null” as command in the docker compose file: After I run docker-compose up I get the following error: ERROR: for serviceName Cannot start service serviceName: b’OCI runtime create failed: container_linux.go:348: starting container process caused “exec: “tail -f /dev/null”: stat tail -f /dev/null: no such file or
In gitlab CI the gitlab runner choose wrong executor
I have the following problem with my Gitlab Pipeline Setup. I recognized that in the bash there is shown “shell runner” but in the .yml file I used “tags: -docker”. If I re-run the job, sometimes it works and uses the right runner, but most of the time not. The is the bash output: Running with gitlab-runner 10.8.0 (079cad9e) on
su and sudo not installed, but I need root permission to install them
I try to yum install package into docker container lambci/lambda:python3.6 I get the interactive console with but both su and sudo are not installed then I try to install anything with root permission is asked How to solve this evil circle ? Answer At least, you can try and run the image as root: That way, in your bash root
Local CircleCI reports “Unexpected environment preparation error: error looking up self container id: Found multiple cgroups for outer container”
I am getting the following error when I run circleci build locally on Ubuntu 18.04. The build runs perfectly inside the hosted CircleCI. CircleCI version: Docker-ce version: I installed Docker exactly as specified on the website, including setting the usergroup. I used the instructions here to install CircleCI, which is this command: sudo curl -o /usr/local/bin/circleci https://circle-downloads.s3.amazonaws.com/releases/build_agent_wrapper/circleci && sudo chmod
Passing environment variables not working with Docker
I am learning how to pass environment variables to Docker containers. While the following works fine, Dockerfile Build & run commands docker ps -a gives docker logs 2a3a69aa7868 gives The following doesn’t work Dockerfile Build & run commands Here the run command gives this, While docker ps -a gives docker logs 249cb045c26a gives nothing Any idea, what is going on
Docker won’t bind to address; says it’s in use but it isn’t
I’m trying to bind two ports from a docker container to a currently unused IP address on one of the host machine’s interfaces. I’m attempting to start the container (which is based on the centos/systemd image) like this: and it fails with the message: Error starting userland proxy: listen tcp 172.19.5.1:22: bind: address already in use. You can see from
Dockerfile not found on Linux hosted agent
I’m trying to package dotnet core application into linux container. Docker build step fail with file not found (even though the same build works on the windows hosted agent with windows containers). I’ve even tried verifying files are there with command line step right in front of the docker build step… files are there, but docker build step fails to
How to pass additional arguments for docker daemon
I have under /etc/sysconfig/docker , the following configuration :- Now I am using docker version 17.03.1-ce on Red Hat Enterprise Linux Server release 7.4 and default storage driver as overlay that is causing lot of build issues due to :- After doing a bit of research on the internet figured out to get rid of this the best solution would