I purchased a linode 1 GB plan recently. I have installed the basic LAMP stack on it.
I wanted to install gitlab on the server. I followed the documentation at: https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/installation.md
The documentation also says the official server is Nginx and I have got Nginx start with no issues.
Problem is when I start the gitlab service using:
sudo service gitlab start
I get:
rm: cannot remove `/home/git/gitlab/tmp/sockets/gitlab.socket': No such file or directory
bash: bundle: command not found
GitLab service started
Related
So basically, I've used this GitHub template https://github.com/aschmelyun/docker-compose-laravel from Andrew Schmelyun
Then installed laravel in src/ folder and run the following commands docker-compose build && docker-compose up -d
Both docker and docker-compose are installed on my computer and the server
Without changing anything. Locally I could see the welcome page on localhost but when I try to access the deployed app on through the IP I get This site can’t be reached
Does anyone have an idea?
Thanks in advance
I am trying to run a private tangle on my computer through linux docker containers.
Therefore I followed the guide over at https://wiki.iota.org/chrysalis-docs/tutorials/one_click_private_tangle
Every step succeeded up until we tried to execute
./private_tangle.sh install
This reports
Error 1
as seen in the screenshot below:
We do net get any further information, is anyone familiar with this error, or has any clue how to get some more information on the error so that we can at least have a clue where to look?
Some further information:
After executing docker ps -a we see that not a single container is running.
I am running on a windows 10 machine
I execute the commands from within ubuntu (version 20.04)
Ubuntu, docker-desktop and docker-desktop-data are all running WSL2
Docker integration with ubuntu is activated
I thought the error could maybe come from no hornet node initially being installed, so I installed a hornet node successfully, according the guide that https://wiki.iota.org/chrysalis-docs/tutorials/one_click_private_tangle. This changed nothing to the Error.
The version of docker and docker-compose are compliant with the requirements
If any more details are needed to help me solve this problem, please let me know.
I used the documentation (https://wiki.iota.org/chrysalis-docs/tutorials/one_click_private_tangle) to install these containers on my local ubuntu 18.04.
My docker version is: 20.10.12
And docker-compose version is: 1.29.2
By following the steps of the tutorial I managed to successfully start all of the containers without trouble.
My guess here would be that the permission of the 'private-tangle.sh' are not correct or that there is permission problem on the docker level.
You should start with checking the permission level of the private-tangle.sh script by using $ls -l
Here is my output -rwxrwxr-x 1 ben ben 9413 Jan 11 11:28 private-tangle.sh
It could also be due to the docker rights if you have to use sudo when executing a docker command it will give some troubles when executing the script.
You need to add yourself to a docker group to be able to run docker commands without sudo. You can do this by running sudo usermod -aG docker $USER with damiaan-vh as $user.
Solution from source https://stackoverflow.com/posts/70665394/edit
Suggesting to downgrade ubuntu version to 18.04 for more stable version.
For reinstalling the docker and docker-compose programs follow this documentations
(docker: https://docs.docker.com/engine/install/ubuntu/ )
(docker-compose: https://docs.docker.com/compose/install/ )
I'm deploying a Flask app using Docker Machine on AWS. The credentials file is located in ~/.aws/:
[default]
aws_access_key_id=AKIAJ<NOT_REAL>7TUVKNORFB2A
aws_secret_access_key=M8G9Zei4B<NOT_REAL_EITHER>pcml1l7vzyedec8FkLWAYBSC7K
region=eu-west-2
Running it as follows:
docker-machine create --driver amazonec2 --amazonec2-open-port 5001 sandbox
According to Docker docs this should work but getting this output:
Error setting machine configuration from flags provided: amazonec2 driver requires AWS credentials configured with the --amazonec2-access-key and --amazonec2-secret-key options, environment variables, ~/.aws/credentials, or an instance role
Before you ask, yes, I set permissions in a such a way that Docker is allowed to access the credentials file.
What should I do ?
Solution found here https://www.digitalocean.com/community/questions/ssh-not-available-when-creating-docker-machine-through-digitalocean
Problem was running Docker as a snap (Ubuntu's repo) instead of official build from Docker. As soon as I uninstalled the Docker snap and installed official build Docker was able to find credentials file immediately.
With Jenkins running on a Ubuntu 14.04 LTS server we began getting crashes on startup of test containers with the following error:
OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:297: copying bootstrap data to pipe caused \"write init-p: broken pipe\"": unknown
Initially it was suspected that this could be due to misconfiguration with local Dockerfiles or the Jenkins server itself, however running:
docker run --rm -i -a stdin -a stdout ubuntu echo 1
Should still work and produced the same issue
It turned out that this was due to a recent Docker update which caused problems with the older 3x kernel found by default on Ubuntu 14.04 LTS
Helpfully it is possible to upgrade the kernel version on 14.04 rather than upgrading the whole OS. It can be done as described on this Ask Ubuntu article, but in short:
sudo apt-get install linux-generic-lts-xenial
sudo reboot
NB: searching the received error message revealed no other current articles online, but searching parts of it sourced a few app-specific forum posts discussing it. For this reason I felt it useful to create a more easily locatable version on here, given it will cover use cases of development, testing or even prod running containers on 14.04.
I have done all the steps by using this tutorial but while running below statement, I am getting the following error. I have created my Digital Ocean VPS host in port 3000.
$ sudo rm /etc/nginx/sites-enabled/default
$ sudo service nginx restart
* Restarting nginx nginx [fail]
$ sudo nginx -t
nginx: [emerg] "listen" directive is not allowed here in /etc/nginx/sites-enabled/hosting:1
nginx: configuration file /etc/nginx/nginx.conf test failed
Check for the solution here:
Nginx unknown directive "upstream" error when deploying Rails
That guy followed the same tutorial, and had the exact same problem. He also posted a solution.
Also, to avoid the issue altogether, you might consider using this plugin: https://github.com/bruno-/capistrano-unicorn-nginx