Docker specific installation version. Dependency failed - docker

Needed a specific version of docker (18.06.1-ce). Removed newer version. Followed: http://www.devopsage.com/how-to-install-docker-on-ubuntu-16-04/ to install.
(ubuntu-16-04)
In the end, systemctl status docker.service got an exception like this:
Dependency failed for Docker Application Container Engine.
Already spent some time googling. No luck.
Q: How it could be fixed?
Thanks.

OK.
Maybe it will save time for someone. The key was to remove previous version like with this command. (Seems something stuck unremoved that caused that issue). Removed again, followed the steps, all started being Ok. again.
To remove:
sudo apt-get remove docker docker-engine docker-ce docker.io
Before I did:
sudo apt-get remove docker docker-ce. // not good

Related

Did I overwrite my old version of Jenkins?

My Jenkins is running on CentOS 7 and I was looking to upgrade my Jenkins version 2.277.4 to 2.375.1. I tried using sudo yum update jenkins to update jenkins. I received this message: “Public key for jenkins-2.375.1-1.1.noarch.rpm is not installed”. I read an article telling me to pull the key from online, so I performed these commands:
sudo wget -O /etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat-stable/jenkins.repo --no-check-certificate
sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key
sudo yum update jenkins
Afterwards, I haven’t been able to correctly start Jenkins. Obviously, I should have just uploaded the new war file instead of using yum update.
Any time I try Sudo systemctl start jenkins I get this warning.
Warning: jenkins.service changed on disk. Run ‘systemctl daemon-reload’ to reload units.
Any suggestions on fixing this issue? Any way to revert back to the old version?
Thank you ahead of time!
**Edit: I tried reloading the daemon and restarting the service. However, my Jenkins start/restart is timing out even though I’ve set the timer to 10 mins.
Additionally, I installed java-11-openjdk during the upgrade, would that cause issues?

Ubuntu, shopsys install via composer, docker, still crashing

I wanna install shopsys via composer and docker, as is recommended.
https://github.com/shopsys/shopsys/blob/master/docs/installation/installation-using-docker-linux.md
I installed git, php-fpm (configured), postgres (configured), composer, docker, docker-compose.
sudo apt install git
sudo apt install php7.2-fpm
sudo apt install postgresql
sudo apt install composer
sudo apt install docker-ce
sudo apt install docker-compose
Everything ok.
I added my user to docker group.
sudo usermod -a -G docker $(whoami)
Ok.
Next I made folder /var/www/html/shopsys, created project shopsys via composer.
composer create-project shopsys/project-base --no-install --keep-vcs
cd project-base/
Then I run this in /var/www/html/shopsys/project-base.
./scripts/install.sh
Everything seems to be ok, until this.
[RuntimeException]
/var/www/html/vendor does not exist and could not be created.
I set rights to 777 for folder /var/www/html, and run it again, but same problem.
The I run this.
sudo composer install
It shows me this error.
....Exception\InvalidConfigurationException]
Invalid configuration for path "monolog.handlers.main": You can only use ex
cluded_http_codes/excluded_404s with a FingersCrossedHandler definition
In ScriptHandler.php line 294:
An error occurred when executing the "'shopsys:domains-urls:configure'" command:
In BaseNode.php line 319:
...\Exception\InvalidConfigurationException]
Invalid configuration for path "monolog.handlers.main": You can only use ex
cluded_http_codes/excluded_404s with a FingersCrossedHandler definition
...
etc., error is quite ugly.
Last error when i run script install.sh.
file_put_contents(/var/www/html/vendor/composer/installed.json): failed to open stream: Permission denied
But this folder does not exist.
ls: cannot access '/var/www/html/vendor/': No such file or directory
Just question, where could be the problem?
Is possible to download sources from some link, extract it, configure and display in web browser with easy way, for example as wordpress?
Thanks.
To solve problem with vendor:
It seems that your UID and GID is different than default 1000, that is set in docker-compose.yml for Linux by default.
To solve your issue you can continue by step 3 in https://github.com/shopsys/shopsys/blob/master/docs/installation/installation-using-docker-linux.md#3-set-the-uid-and-gid-to-allow-file-access-in-mounted-volumes
You found issue with installation script, I have created issue on GitHub.
To solve problem with Invalid configuration for path "monolog.handlers.main":
Currently there is problem with new minor version (3.4.0) of symfony/monolog-bundle that created BC break. There is already created issue about this problem and there is already merged fix in Shopsys master.
To solve problem in your project you have to add
"symfony/monolog-bundle": ">=3.4.0", in conflict section in your composer.json file and then run composer install again.
We are trying to answer questions on stackoverflow as soon as possible, but we also have Slack where is many users and you might get your question answered much faster.

docker removed, but is still updating

I used docker for a while, but i don't need it anmyore. So i removed it from my Ubuntu 16.04. When i try "sudo apt-get remove docker" it says that there is nothing, but when i run "sudo apt-get update" i get many lines like this:
Ign:45 https://download.docker.com/linux/ubuntu §(lsb_release/stable amd64 DEP-11 Metadata
So it's still updating docker.
Does anyone know how to remove docker completely from Ubuntu 16.04?
As sanath already stated you still have entries in /etc/apt/source.list for the docker package repository. You need to remove these (look for lines containing docker in that file and remove them).
To explain what these entries are:
/etc/apt/sorce.list lists all sources for packages which you can install/upgrade using apt. When you followed the steps in the installation of docker you added a line with the address of the docker package repository there. Now apt update always polls that repo to check if it contains any upgrades of a package you have installed.
Now because that address contains docker you falsely asume that you still have docker installed, which is not the case. Docker is simply part of the url of one of the repositories that is queried for updates.
It's because some of the entries are still present in.
nano /etc/apt/source.list
Remove lines which is having docker repository.
Then do apt-get update

Raspbian docker: Error response from daemon: cgroups: memory cgroup not supported on this system: unknown

I am new to docker, I plug my PI3 to test some stuff and I'm already facing an error, I can't figured that out myself.
So I freshly install raspbian and docker.
That's my install log
Then I try the classic hello-word test
and there is the log
It looks 17.11.0 has the problem.
Could you try to install the old one as below ?
$ sudo apt install docker-ce=17.09.0~ce-0~raspbian
Or wait for the fix.
(2017.12.5)
It looks 2017-11-29-raspbian-stretch has same issue. To avoid upgrading by apt upgrade, Do: sudo apt-mark hold docker-ce.
And unhold when it fixes.
Another solution is to add cgroup_enable=memory cgroup_memory=1 in /boot/cmdline.txt at the end of the line and reboot.

OpenSuse - Can't install Rails: File not found on medium

I'm trying to set up a Ruby on Rails environment within OpenSuse, but I've encountered a problem. When running sudo zypper install rubygem-railties-3_2 all I get is File '/repodata/repomd.xml' not found on medium 'http://download.opensuse.org/repositories/Banshee/12.1/'. So something seems to be wrong at their side.
Is there anyone who as a workaround for, or more info about, this problem?
When running the command $ sudo zypper up I was receiving a similar error:
File ... not found on medium http:// ...
Detailed error:
File './x86_64/libxkbcommon0-0.7.2-48.2.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_42.3/'
The solution which worked for me was to run $ sudo zypper ref before running $ sudo zypper up
Obviously, you have setup an additional repository for Banshee for a very old opensuse version. Opensuse only keeps its repositories alive for the last two two releases to the current release. For this reason, you get this error. You can disable or remove the repositorium to resolve the error.
In order to install packages that are not part of the currently configured repositories, it is the easiest to use the one-click install available at https://software.opensuse.org/search .

Resources