I want to install docker 1.3.1 on my centos 6.5 environment but I have no idea how to find it in the epel. I'm quite new to docker. Can anyone help me out? Thanks
Clearly stated in the Docker documentation:
Docker runs on CentOS 7.X.
CentOS 6.5 is not CentOS 7.X. Docker is not available for your old operating system.
Furthermore, you didn't give any details about your computer, but you should remain aware that Docker only works on 64-bit systems.
By the way, you should take better care of your computer; in CentOS, the minor version number is updated automatically by the package manager. So the fact that you are two versions behind (CentOS 6 is currently on 6.7) indicates that you are not performing updates to your packages, and could have various security vulnerabilities. You should update your system regularly, by simply running yum update.
Related
I was told it's better not to use latest in Docker File, but how can I find alternatives?
According to: https://ubuntu.com/download/desktop the latest version of ubuntu is Ubuntu 22.04.1 LTS but when I go to: https://hub.docker.com/_/ubuntu/tags I see strange tags like: bionic what is that?
and 22.10 this is a future version? how is that possible?
and while I could fine 22.04 I could not find 22.04.1
There are many problems involving the usage of latest tag on a docker image. The application is constantly changing and with it its architecture as well. While pulling an image with the latest tag, you use these changes as well. This may be good in a personal project sometimes but in a large scale application, you dont want your application to change drastically. Example:
While working on a dockerized application, we incorporated db connector to session storage redis db, the connector connected to redis at the start of the application and if it was unsuccessful, the application would not start. Every update/change on the host machine with running application meant deploying redis as well as we were using the latest tag.
22.04 Ubuntu is the latest LTS build, but there also is experimental 22.10 (ref. Ubuntu 22.10
I am new learner for Docker.I have a very simple question.
I want my application to work on Linux system but I am writing application in Windows.So do I need to install Docker for Windows or Linux?
If I run using Docker for Linux,i am not getting option to run in windows and it is getting failed(I understand it might be some other unrelated error) but I need to confirm if my approach is correct or not.
Am I right in installing Docker for Linux?
Also,in case I plan to move to AWS, what docker I need in that case.
Thanks
Consider docker as any software. if your OS is windows you install windows version of a software. if your is a linux distro then you install linux version of a software.
So you need to install docker for windows afterwards you can install any docker image/container you want under your operating system. Could be windows, linux or anything else.
We are running docker 1.7.1, build 786b29d on RHEL 6.7. Recently we have had multiple times when the docker daemon locked up and we had to reboot the machine to get it back.
A typical scenario is that a container that has been running fine for weeks suddenly starts throwing errors. Sometime we can restart the container and all is well. But other times all docker commands will hang, and restarting the daemon fails, and I see this in a ps:
4 Z root 4895 1 0 80 0 - 0 exit Aug23 ? 00:01:24 [docker]
Looking in the system log I've seen this:
device-mapper: ioctl: unable to remove open device docker-253:6-1048578-317bb6ad40cded3fbfd752d95551861c2e4ef08dffc1186853fea0e85da6b12b
INFO: task docker:16676 blocked for more than 120 seconds.
Not tainted 2.6.32-573.12.1.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
docker D 000000000000000b 0 16676 1 0x00000080
ffff88035ef13ea8 0000000000000082 ffff88035ef13e70 ffff88035ef13e6c
ffff88035ef13e28 ffff88062fc29a00 0000376c85170937 ffff8800283759c0
0000000000000400 00000001039d40c7 ffff8803000445f8 ffff88035ef13fd8
Call Trace:
[] _mutexlock_slowpath+0x96/0x210
[] ? wake_up_process+0x15/0x20
[] mutex_lock+0x2b/0x50
[] sync_filesystems+0x26/0x150
[] sys_sync+0x17/0x40
[] system_call_fastpath+0x16/0x1b
The latest docker version is 1.12.1 and we are on 1.7.1. Can or should I install a new version? 1.7.1 is the version yum installs. If I did want a new version how would I install that (sorry if that is a dumb question, I am not a sys admin).
Googling, I found on this on a Red Hat site "Red Hat does not recommend running any version of Docker on any RHEL 6 releases." We have been running docker on RHEL 6 for a few years, so this confuses me. Upgrading to RHEL 7 is not really an option for us right now.
Can anyone shed any light on these issue? We need docker to work reliably without having to reboot often.
Docker 1.7.1 is really old by today's standards. There have been hundreds of bugs fixed, enhancements to driver stacks, security patches, and valuable features added in the versions since. It looks like you're having a issue with your storage stack, and there is a good chance this is fixed in a newer version.
Docker has stated that default versions in package management systems like yum and apt can be way out of date, and that you should use their repo. The best way to do this is add their Yum repo information to your system so you can install it like other packages. The instructions are here: Installation on Red Hat Enterprise Linux.
Note: This will allow you to install Docker, and the service will be called docker, but the package is docker-engine. This has confused some people in the past.
yum install docker-engine
Docker has also provided a script that does this to make things easier (run as admin/root):
curl -fsSL https://get.docker.com/ | sh
Don't use a RHEL6 based system.
RHEL6 uses a 2.6 kernel with backported fixes to keep Docker working. Docker would normally require a 3.10+ kernel. Docker dropped support for RHEL6 from v1.8 on so it's unlikely there will be any more packages for it.
If you must use RHEL6, don't use the default loopback devicemapper for storage. Setup an LVM thin pool for Docker to use.
We are currently running Red Hat 5. But I saw documentation that says docker is only supported on Red Hat 7. So we have to upgrade to Red Hat 7 or we can't use docker at all on RHEL 5? Alternatively we can consider to switch to Ubuntu.
How do others solve the similar issue?
You will need to upgrade from RHEL5 to use Docker.
The official Docker release deprecated RHEL6 support from 1.7 (and inadvertently broke it in 1.7.0 but fixed in 1.7.1). Support for RHEL6 was dropped in Docker 1.8. Since then, a RHEL7 based distro with a 3.10+ kernel has been required.
There is a docker-io-1.7.1-2 package available on EPEL for RHEL6.5+ based distros. RHEL6 runs an older 2.6 kernel with back ported fixes so docker can work. This kernel must be at 2.6.32-431 or higher.
RHEL doesn't support AUFS which is the most commonly used Docker storage driver. By default RHEL uses a loopback storage driver which is not production ready. The EPEL packages provide docker-storage-setup to setup thin provisioned LVM. You need to do this setup manually if you want to run the docker.com packages.
Personally I would recommend going with a recent debian based distribution running the official docker packages for timely updates. If you are on EC2, Amazons AMI will do nicely though.
I've bought a Debian 8 VPS for 3e per month https://www.pulseheberg.com/vps/simple.
I would like to install docker engine but it not works ( cause it need a kernel >= 3.10)
Do you have any idea for install docker on my server ?
Related?
You can't. Sorry to bear the bad news.
Docker backport-supports kernel 3.10 but not below. Here is a copy/paste from their doc:
Prerequisites
Docker requires a 64-bit installation regardless of your Debian version. Additionally, your kernel must be 3.10 at minimum. The latest 3.10 minor version or a newer maintained version are also acceptable.
Kernels older than 3.10 lack some of the features required to run Docker containers. These older versions are known to have bugs which cause data loss and frequently panic under certain conditions.