Unable to locate package `docker-ce` on a 64bit ubuntu

Unable to locate package `docker-ce` on a 64bit ubuntu

Im trying to install Docker on a Ubuntu 64 machine following the official installation guide. Sadly Ubuntu seems it is not able to locate the docker-ce package. Any idea to fix it or at least to track what is happening Here some details for you... uname --all; sudo grep docker etcaptsources.list; sudo apt-get install docker-ce Linux ubuntu 4.4.0-62-generic 83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNULinux deb archamd64 https:download.docker.comlinuxubuntu xenial stable. deb-src archamd64 https:download.docker.comlinuxubuntu xenial stable. Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package docker-ce

You can install docker-ce on Ubuntu 16.04 as follows: sudo apt-get install apt-transport-https ca-certificates curl software-properties-common curl -fsSL https:download.docker.comlinuxubuntugpg sudo apt-key add - sudo add-apt-repository deb archamd64 https:download.docker.comlinuxubuntu xenial stable sudo apt-get update Run the following apt-cache search docker-ce sample output: docker-ce - Docker: the open-source application container engine Install docker-ce: sudo apt-get install docker-ce Update Jan 03 2018 installing docker-ce on Ubuntu 17.10 : docker-ce package is available on the official docker Ubutu Artful repository , to install it use the following commands : sudo apt install apt-transport-https ca-certificates curl software-properties-common curl -fsSL https:download.docker.comlinuxubuntugpg sudo apt-key add - sudo add-apt-repository deb archamd64 https:download.docker.comlinuxubuntu artful stable sudo apt update sudo apt install docker-ce Update Apr 29 2018 : Installing docker-ce on Ubuntu 18.04 bionic A testing note the test instead of stable release is available for Ubuntu 18.04 it can installed as follows: sudo apt install apt-transport-https ca-certificates curl software-properties-common curl -fsSL https:download.docker.comlinuxubuntugpg sudo apt-key add - sudo add-apt-repository deb archamd64 https:download.docker.comlinuxubuntu bionic test sudo apt update sudo apt install docker-ce The above command will install the testing release available on the pooltestamd64 docker --version Docker version 18.05.0-ce-rc1, build 33f00ce

For anyone who is using Ubuntu 17.10 artful and having this problem: From https:docs.docker.comengineinstallationlinuxdocker-ceubuntu To install Docker CE, you need the 64-bit version of one of these Ubuntu versions: Artful 17.10 Docker CE 17.11 Edge only Zesty 17.04 Xenial 16.04 LTS Trusty 14.04 LTS and: To add the edge or test repository, add the word edge or test or both after the word stable in the commands So if you are using Ubuntu 17.10 artful, you need to add this: sudo add-apt-repository deb archamd64 https:download.docker.comlinuxubuntu lsb_release -cs stable edge Noticing edge word is added. If you already ran this command before without edge. You can edit the source.list file at etcaptsources.list. After that, refresh and install docker-ce as usual: sudo apt-get update sudo apt-get install docker-ce

Looks like docker will be in official repository after December docker-ce release stable. Then this repository: sudo add-apt-repository deb archamd64 https:download.docker.comlinuxubuntu artful stable should work. Meanwhile there should be soon available edge release on sudo add-apt-repository deb archamd64 https:download.docker.comlinuxubuntu artful edge But its not available now yet. But v17.11.0-ce-rc4 was released yesterday, so i would expect it any day now. So for now I used package from 17.04 repo as GAD3R is suggesting. link to github issue.

Try using: curl -fsSL https:download.docker.comlinuxubuntugpg sudo apt-key add - sudo add-apt-repository deb archamd64 https:download.docker.comlinuxubuntu lsb_release -cs stable sudo apt-get update sudo apt install docker.io

None of the above worked for me. I removed docker completely, then went and manually removed the docker files in var. Reinstalled and running perfectly afterwards.

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

Skipping acquire of configured file 'contrib/binary-i386/Packages' as repository … doesn't support architecture 'i386'

Skipping acquire of configured file 'contrib/binary-i386/Packages' as repository … doesn't support architecture 'i386' I installed Ubuntu 18.04 and then while installing Virtualbox i get the i386 error message after I did: sudo apt-get update Get:1 http:nl.archive.ubuntu.comubuntu bionic InRelease 242 kB Hit:2 http:security.ubuntu.comubuntu bionic-security InRelease Hit:3 http:ppa.launchpad.netdanielrichter2007grub-customizerubuntu bionic InRelease Hit:4 http:nl.archive.ubuntu.comubuntu bionic-updates InRelease Hit:5 http:nl.archive.ubuntu.comubuntu bionic-backports InRelease Get:6 http:download.virtualbox.orgvirtualboxdebian bionic InRelease 4429 B Get:7 http:download.virtualbox.orgvirtualboxdebian bioniccontrib amd64 Packages 1426 B Fetched 248 kB in 1s 209 kBs Reading package lists... Done N: Skipping acquire of configured file contribbinary-i386Packages as repository http:download.virtualbox.orgvirtualboxdebian bionic InRelease doesnt support architecture i386 ...
Далее...

Connection string for MariaDB using ODBC

Connection string for MariaDB using ODBC What is the connection string for using MariaDB with ODBC Im guessing its something like DRIVERMariaDB ODBC 5.1 Driver; SERVERLOCALHOST; PORT3306; DATABASEDatabaseName; UIDroot; PASSWORDpassword;OPTION3; Connection strings seems to show strings for MySQL but not MariaDB. MariaDB seems to have a lot of connection strings for Access, SQL Lite, excel, etc ... What have I missed Although this is late answer, but MariaDB have that documented here SQLWCHAR ConnStr LDriverMariaDB ODBC 2.0 Driver;Serverlocalhost;UIDodbc_user;PWDodbc_pw;DBodbc_test;Port3306;
Далее...

Celery like system based on django channels

Celery like system based on django channels According to the docs of django channels: http:channels.readthedocs.ioenlatestconcepts.htmlhighlightcelerynext-steps One thing channels do not do, however, is guarantee delivery. If you need certainty that tasks will complete, use a system designed for this with retries and persistence e.g. Celery, or alternatively make a management command that checks for completion and re-submits a message to the channel if nothing is completed rolling your own retry logic, essentially. I worked with celery some years ago. Yes, it is great, it is big, it is too much. I would like to avoid it. I am searching a simple tasks queue with guarantee delivery and a re-submission on failure. An other alternative would be python-rq. But this has other disadvantages like using pickle data format instead of json. A friend gave me an advice: https:github.comfurious-lukedjango-cq Looks good. From the docs An attempt to implement a distributed task queue ...
Далее...