Why the RUN command in this dockerfile is not working

Why the RUN command in this dockerfile is not working

I have a docker image MyBaseImage where I have Open SSH server installed. Now in the docker file, I have the following. Download base image FROM MyBaseImage RUN service ssh start I build the new image by typing docker build . Docker builds the image fine, giving the following information. Step 12 : FROM MyBaseImage --- 56f88e347f77 Step 22 : RUN service ssh start --- Running in a1afe0c2ce71 Starting OpenBSD Secure Shell server sshd OK Removing intermediate container a1afe0c2ce71 --- 7879cebe8b6a But when I run the new image by typing docker run -it 7879cebe8b6a Docker builds the image fine, giving the following information. If I type service ssh status inside the terminal of that container, it says sshd is not running I have to then manually start the Open SSH server by typing service ssh start. What could be the reason for it

Depending on which distro of linux you are using command slightly changes: If you are using ubuntu your start command should work. But if your base image is centosRHEL try below: service sshd start

Комментарии

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

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

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 ...
Далее...