Following the documentation, I am trying to setup my own gitlab using the docker container.
In the volumes section, the host path /srv/gitlab is a network share.
I have a group with name docker and the current user belongs to that group. While mounting the network share, I specified the uid=,gid=docker.
My problem is, the docker container starts but keeps crashing with some permission error. I am pretty sure its because of the network share.
Anyone has any idea on setting correct permissions for the network share before starting the gitlab container?
This is how the error looks like:
[2016-09-07T23:18:49+00:00] FATAL: Stacktrace dumped to /opt/gitlab/embedded/cookbooks/cache/chef-stacktrace.out
[2016-09-07T23:18:49+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-09-07T23:18:49+00:00] ERROR: directory[/etc/gitlab] (gitlab::default line 26) had an error: Errno::EACCES: Permission denied # chown_internal - /etc/gitlab
[2016-09-07T23:18:49+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Related
This question already has answers here:
Docker: "no matching manifest for windows/amd64 in the manifest list entries"
(25 answers)
Closed 2 years ago.
Having failed to install azerothcore normally, I have now tried to install it using docker.
But I am already running into an issue, probably because I am not very experienced with docker.
When I input ./bin/acore-docker-build, it fails at step one, outputting this message:
Sending build context to Docker daemon 862.4MB
Step 1/11 : FROM ubuntu:bionic
bionic: Pulling from library/ubuntu
no matching manifest for windows/amd64 10.0.18362 in the manifest list entries
Unable to find image 'acbuild:latest' locally
C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: pull access denied for acbuild, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'C:\Program Files\Docker\Docker\resources\bin\docker.exe run --help'.
I am not sure what I am supposed to do about this. I am logged into a basic docker account. I went to the docker.exe referenced in the above message and changed permissions for the account running docker to have full permissions. No change. I ran git as administrator. No change.
What should I be doing differently?
Thanks for reading. Willing to clarify anything.
Also, I am using windows 10.
You probably need to have Docker for Desktop opened up and Docker daemon running (icon from bottom left should be green).
I'm trying to set up VSCode so I can work on a project which resides inside a docker container. There's a recently published extension Remote Development which seems to enable just that.
I followed detailed official instructions on creating .devcontainer/devcontainer.json and setting up remote by running Remote-Containers: Reopen Folder in Container, however, even with official/provided containers and settings I get the error:
Setting up container for folder: /home/ilijas/<path_to>/workspace
Error: (HTTP code 500) server error - linux spec user: unable to find user ilijas: no matching entries in passwd file
at /home/ilijas/.vscode-insiders/extensions/ms-vscode-remote.remote-containers-0.53.0/dist/extension.js:1:151013
at /home/ilijas/.vscode-insiders/extensions/ms-vscode-remote.remote-containers-0.53.0/dist/extension.js:1:150976
at m.buildPayload (/home/ilijas/.vscode-insiders/extensions/ms-vscode-remote.remote-containers-0.53.0/dist/extension.js:1:150986)
at IncomingMessage.<anonymous> (/home/ilijas/.vscode-insiders/extensions/ms-vscode-remote.remote-containers-0.53.0/dist/extension.js:1:150486)
at IncomingMessage.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1090:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
In my first attempts I tried to mount a local workspace to remote one, however, since I couldn't resolve this user-not-found error, I removed all of the arguments inside docker settings which regarded user, just to make one dummy container work. I had no success. I know this is a fresh extension, but still, I hope someone can help.
Essentially, removing all the previous docker containers solved the issue.
Reference GitHub issue:
The container has a label with the folder as the value, so it can be found again. When you close the window, the container is only stopped, not removed, for later use. (You could have some changes inside the container you want to keep. Also: Reusing an existing container is slightly faster.)
Hi thank you for all guys watching this article.
Cuz I want to use Hyperledger composer, I deployed orderer, peer, ca and other things. And I got success until creating channel and joining channel
(I believe that this is true cuz I finished making channels, joining peers to join that channel, installing and instantiating chaincode.)
So after that I did
"composer network install" command and I got error that there is no response from peers.
(And "Response from attempted peer comms was an error: Error: 14 UNAVAILABLE: EOF")
So I started to think that there is a problem on the file named "connection.json". But I don't know specifically how to edit that file.
I got response like below commanding "docker service ls" and "docker network inspect fabric"
enter image description here
and my connection.json file looks like this
enter image description here
And I referred to this page to do Hyperledger Fabric on multiple hosts.
https://medium.com/#malliksarvepalli/hyperledger-fabric-on-multiple-hosts-using-docker-swarm-and-compose-f4b70c64fa7d
And this is the screenshot after installing business network
enter image description here
I think your fabric network is not running!
open a terminal and go to your fabric-dev-servers directory and ./startFabric.sh
if you facing any error there, like some container already exists do ./teardownFabric.sh first and then run above start command again.
once a network is running successfully then you need to create admin card by running ./createPeerAdminCard.sh
Could you confirm that all orderer, peers and CAs are successfully launched on each machine? 'docker ps' command shows which services are running. If you use 'docker ps -a', you can find which service is stopped.
From the all of docker-compose files, following container name should be listed by 'docker ps'
orderer
: orderer
org1
: ca1
: org1peer0
: org1peer1
: org1cli
org2
: ca2
: org2peer0
: org2peer1
: org2cli
Could you check this is correct?
Are you running this project on 3 machines or 3 cloud instances?
Can anyone help me make sense of the below error and others like it? I've Googled around, but nothing makes sense for my context. I download my Docker Image, but the container refuses to start. The namespace referenced is not always 26, but could be anything from 20-29. I am launching my Docker container onto an EC2 instance and pulling the image from AWS ECR. The error is persistent no matter if I re-launch the instance completely or restart docker.
docker: Error response from daemon: oci runtime error:
container_linux.go:247: starting container process caused
"process_linux.go:334: running prestart hook 0 caused \"error running
hook: exit status 1, stdout: , stderr: time=\\\"2017-05-
11T21:00:18Z\\\" level=fatal msg=\\\"failed to create a netlink handle:
failed to set into network namespace 26 while creating netlink socket:
invalid argument\\\" \\n\"".
Update from my Github issue: https://github.com/moby/moby/issues/33656
It seems like the DeepSecurity agent (ds_agent) running on a container with Docker can cause this issue invariably. A number of other users reported this problem, causing me to investigate. I previously installed ds_agent on these boxes, before replacing it with other software as a business decision, which is when the problem went away. If you are having this problem, might be worthwhile to check if you are running the ds_agent process, or other similar services that could be causing a conflict using 'htop' as the user in the issue above did.
Did you try running it with the --privileged option?
If it still doesn't run, try adding --security-opts seccomp=unconfined and either --security-opts apparmor=unconfined or --security-opts selinux=unconfined depending whether you're running Ubuntu or a distribution with SELinux enabled, respectively.
If it works, try substituting the --privileged option with --cap-add=NET_ADMIN` instead, as running containers in privileged mode is discouraged for security reasons.
I am unable to run rabbitmq using marathon/mesos framework. I have tried it with rabbitmq images available in docker hub as well as custom build rabbitmmq docker image. In the mesos slave log I see the following error:
E0222 12:38:37.225500 15984 slave.cpp:2344] Failed to update resources for container c02b0067-89c1-4fc1-80b0-0f653b909777 of executor rabbitmq.9ebfc76f-ba61-11e4-85c9-56847afe9799 running task rabbitmq.9ebfc76f-ba61-11e4-85c9-56847afe9799 on status update for terminal task, destroying container: Failed to determine cgroup for the 'cpu' subsystem: Failed to read /proc/13197/cgroup: Failed to open file '/proc/13197/cgroup': No such file or directory
On googling I could find one hit as follows
https://github.com/mesosphere/marathon/issues/632
Not sure if this is the issue even I am facing. Anyone tried running rabbitmq using marathon/mesos/docker?
Looks like the process went away (likely crashed) before the container was set up. You should check stdout and stderr to see what happened, and fix the root issue.
"cmd": "", is the like'y culprit. I'd look at couchbase docker containers for a few clues on how to get it working.