systemd not autorestarting the last docker container after it crashes or kill -9 or docker stop service












0














I have 3 docker containers whose unit files are as below. Autorestart works for 1st and 2nd in the dependency chain but doesnot work for last. I replaced docker containers with some test bash scripts with same relationships and autorestart seem to work fine. So it is issue with auto restart with docker container on the edge(edge case). The issue is important because we cannot automatically recover after last container crashes for some reason.



container1(nehm) -> container 2(neca) > container 3(proxy)



container1



[Unit]

Description=NEHM service for LosAngelesTESRP

Requires=cassandra.service rabbitmq.service consul.service vesta-neca-LosAngelesTESRP.service

BindsTo=cassandra.service rabbitmq.service consul.service vesta-neca-LosAngelesTESRP.service

After=network.target remote-fs.target nss-lookup.target docker.service cassandra.service rabbitmq.service consul.service



[Install]

WantedBy=multi-user.target



[Service]

ExecStart=/opt/vesta/bin/service-wrapper vesta-nehm-LosAngelesTESRP

Type=forking

KillMode=mixed

PIDFile=/var/run/vesta-nehm-LosAngelesTESRP.pid

ExecStartPre=/bin/sh /etc/vesta/network/LosAngelesTESRP start

ExecStop=/usr/bin/docker stop vesta-nehm-LosAngelesTESRP

ExecStopPost=/bin/sh /etc/vesta/network/LosAngelesTESRP stop

RestartSec=30

Restart=always

StartLimitInterval=600

StartLimitBurst=3


container2



[Unit]

Description=neca service for LosAngelesTESRP

Requires=vesta-proxy-LosAngelesTESRP.service

BindsTo=vesta-nehm-LosAngelesTESRP.service vesta-proxy-LosAngelesTESRP.service

PartOf=vesta-nehm-LosAngelesTESRP.service

After=network.target remote-fs.target nss-lookup.target docker.service vesta-nehm-LosAngelesTESRP.service



[Install]

WantedBy=multi-user.target



[Service]

ExecStart=/opt/vesta/bin/service-wrapper vesta-neca-LosAngelesTESRP

Type=forking

KillMode=mixed

PIDFile=/var/run/vesta-neca-LosAngelesTESRP.pid

ExecStop=/usr/bin/docker stop vesta-neca-LosAngelesTESRP

RestartSec=30

Restart=always

StartLimitInterval=600

StartLimitBurst=3


container3 which has issue



[Unit]

Description=Proxy service for LosAngelesTESRP

BindsTo=vesta-neca-LosAngelesTESRP.service

PartOf=vesta-neca-LosAngelesTESRP.service

After=network.target network-interface-LosAngelesTESRP.service remote-fs.target nss-lookup.target docker.service vesta-neca-LosAngelesTESRP.service



[Install]

WantedBy=multi-user.target



[Service]

ExecStart=/opt/vesta/bin/service-wrapper vesta-proxy-LosAngelesTESRP

Type=forking

KillMode=mixed

PIDFile=/var/run/vesta-proxy-LosAngelesTESRP.pid

ExecStop=/usr/bin/docker stop vesta-proxy-LosAngelesTESRP

RestartSec=30



Restart=always

StartLimitInterval=600

StartLimitBurst=3







[root@services-2 system]# systemctl status vesta-proxy-LosAngelesTESRP.service

● vesta-proxy-LosAngelesTESRP.service - Proxy service for LosAngelesTESRP

   Loaded: loaded (/etc/systemd/system/vesta-proxy-LosAngelesTESRP.service; disabled; vendor preset: disabled)

   Active: inactive (dead) since Wed 2018-12-19 10:05:48 PST; 1h 19min ago

  Process: 2763 ExecStop=/usr/bin/docker stop vesta-proxy-LosAngelesTESRP (code=exited, status=0/SUCCESS)

  Process: 2533 ExecStart=/opt/vesta/bin/service-wrapper vesta-proxy-LosAngelesTESRP (code=exited, status=0/SUCCESS)

 Main PID: 2559



Dec 19 10:05:47 services-2.amber.lab systemd[1]: Installed new job vesta-proxy-LosAngelesTESRP.service/stop as 18224

Dec 19 10:05:47 services-2.amber.lab systemd[2763]: Executing: /usr/bin/docker stop vesta-proxy-LosAngelesTESRP

Dec 19 10:05:48 services-2.amber.lab docker[2763]: vesta-proxy-LosAngelesTESRP

Dec 19 10:05:48 services-2.amber.lab systemd[1]: Child 2763 belongs to vesta-proxy-LosAngelesTESRP.service

Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service: control process exited, code=exited status=0

Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service got final SIGCHLD for state stop

Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service changed stop -> dead

Dec 19 10:05:48 services-2.amber.lab systemd[1]: Job vesta-proxy-LosAngelesTESRP.service/stop finished, result=done

Dec 19 10:05:48 services-2.amber.lab systemd[1]: Stopped Proxy service for LosAngelesTESRP.

Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service: cgroup is empty





systemd







share|improve this question





























    0














    I have 3 docker containers whose unit files are as below. Autorestart works for 1st and 2nd in the dependency chain but doesnot work for last. I replaced docker containers with some test bash scripts with same relationships and autorestart seem to work fine. So it is issue with auto restart with docker container on the edge(edge case). The issue is important because we cannot automatically recover after last container crashes for some reason.



    container1(nehm) -> container 2(neca) > container 3(proxy)



    container1



    [Unit]
    
Description=NEHM service for LosAngelesTESRP
    
Requires=cassandra.service rabbitmq.service consul.service vesta-neca-LosAngelesTESRP.service
    
BindsTo=cassandra.service rabbitmq.service consul.service vesta-neca-LosAngelesTESRP.service
    
After=network.target remote-fs.target nss-lookup.target docker.service cassandra.service rabbitmq.service consul.service
    

    
[Install]
    
WantedBy=multi-user.target
    

    
[Service]
    
ExecStart=/opt/vesta/bin/service-wrapper vesta-nehm-LosAngelesTESRP
    
Type=forking
    
KillMode=mixed
    
PIDFile=/var/run/vesta-nehm-LosAngelesTESRP.pid
    
ExecStartPre=/bin/sh /etc/vesta/network/LosAngelesTESRP start
    
ExecStop=/usr/bin/docker stop vesta-nehm-LosAngelesTESRP
    
ExecStopPost=/bin/sh /etc/vesta/network/LosAngelesTESRP stop
    
RestartSec=30
    
Restart=always
    
StartLimitInterval=600
    
StartLimitBurst=3


    container2



    [Unit]
    
Description=neca service for LosAngelesTESRP
    
Requires=vesta-proxy-LosAngelesTESRP.service
    
BindsTo=vesta-nehm-LosAngelesTESRP.service vesta-proxy-LosAngelesTESRP.service
    
PartOf=vesta-nehm-LosAngelesTESRP.service
    
After=network.target remote-fs.target nss-lookup.target docker.service vesta-nehm-LosAngelesTESRP.service
    

    
[Install]
    
WantedBy=multi-user.target
    

    
[Service]
    
ExecStart=/opt/vesta/bin/service-wrapper vesta-neca-LosAngelesTESRP
    
Type=forking
    
KillMode=mixed
    
PIDFile=/var/run/vesta-neca-LosAngelesTESRP.pid
    
ExecStop=/usr/bin/docker stop vesta-neca-LosAngelesTESRP
    
RestartSec=30
    
Restart=always
    
StartLimitInterval=600
    
StartLimitBurst=3


    container3 which has issue



    [Unit]
    
Description=Proxy service for LosAngelesTESRP
    
BindsTo=vesta-neca-LosAngelesTESRP.service
    
PartOf=vesta-neca-LosAngelesTESRP.service
    
After=network.target network-interface-LosAngelesTESRP.service remote-fs.target nss-lookup.target docker.service vesta-neca-LosAngelesTESRP.service
    

    
[Install]
    
WantedBy=multi-user.target
    

    
[Service]
    
ExecStart=/opt/vesta/bin/service-wrapper vesta-proxy-LosAngelesTESRP
    
Type=forking
    
KillMode=mixed
    
PIDFile=/var/run/vesta-proxy-LosAngelesTESRP.pid
    
ExecStop=/usr/bin/docker stop vesta-proxy-LosAngelesTESRP
    
RestartSec=30
    

    
Restart=always
    
StartLimitInterval=600
    
StartLimitBurst=3
    





    
[root@services-2 system]# systemctl status vesta-proxy-LosAngelesTESRP.service
    
● vesta-proxy-LosAngelesTESRP.service - Proxy service for LosAngelesTESRP
    
   Loaded: loaded (/etc/systemd/system/vesta-proxy-LosAngelesTESRP.service; disabled; vendor preset: disabled)
    
   Active: inactive (dead) since Wed 2018-12-19 10:05:48 PST; 1h 19min ago
    
  Process: 2763 ExecStop=/usr/bin/docker stop vesta-proxy-LosAngelesTESRP (code=exited, status=0/SUCCESS)
    
  Process: 2533 ExecStart=/opt/vesta/bin/service-wrapper vesta-proxy-LosAngelesTESRP (code=exited, status=0/SUCCESS)
    
 Main PID: 2559
    

    
Dec 19 10:05:47 services-2.amber.lab systemd[1]: Installed new job vesta-proxy-LosAngelesTESRP.service/stop as 18224
    
Dec 19 10:05:47 services-2.amber.lab systemd[2763]: Executing: /usr/bin/docker stop vesta-proxy-LosAngelesTESRP
    
Dec 19 10:05:48 services-2.amber.lab docker[2763]: vesta-proxy-LosAngelesTESRP
    
Dec 19 10:05:48 services-2.amber.lab systemd[1]: Child 2763 belongs to vesta-proxy-LosAngelesTESRP.service
    
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service: control process exited, code=exited status=0
    
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service got final SIGCHLD for state stop
    
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service changed stop -> dead
    
Dec 19 10:05:48 services-2.amber.lab systemd[1]: Job vesta-proxy-LosAngelesTESRP.service/stop finished, result=done
    
Dec 19 10:05:48 services-2.amber.lab systemd[1]: Stopped Proxy service for LosAngelesTESRP.
    
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service: cgroup is empty





    systemd







    share|improve this question



























      0












      0








      0







      I have 3 docker containers whose unit files are as below. Autorestart works for 1st and 2nd in the dependency chain but doesnot work for last. I replaced docker containers with some test bash scripts with same relationships and autorestart seem to work fine. So it is issue with auto restart with docker container on the edge(edge case). The issue is important because we cannot automatically recover after last container crashes for some reason.



      container1(nehm) -> container 2(neca) > container 3(proxy)



      container1



      [Unit]
      
Description=NEHM service for LosAngelesTESRP
      
Requires=cassandra.service rabbitmq.service consul.service vesta-neca-LosAngelesTESRP.service
      
BindsTo=cassandra.service rabbitmq.service consul.service vesta-neca-LosAngelesTESRP.service
      
After=network.target remote-fs.target nss-lookup.target docker.service cassandra.service rabbitmq.service consul.service
      

      
[Install]
      
WantedBy=multi-user.target
      

      
[Service]
      
ExecStart=/opt/vesta/bin/service-wrapper vesta-nehm-LosAngelesTESRP
      
Type=forking
      
KillMode=mixed
      
PIDFile=/var/run/vesta-nehm-LosAngelesTESRP.pid
      
ExecStartPre=/bin/sh /etc/vesta/network/LosAngelesTESRP start
      
ExecStop=/usr/bin/docker stop vesta-nehm-LosAngelesTESRP
      
ExecStopPost=/bin/sh /etc/vesta/network/LosAngelesTESRP stop
      
RestartSec=30
      
Restart=always
      
StartLimitInterval=600
      
StartLimitBurst=3


      container2



      [Unit]
      
Description=neca service for LosAngelesTESRP
      
Requires=vesta-proxy-LosAngelesTESRP.service
      
BindsTo=vesta-nehm-LosAngelesTESRP.service vesta-proxy-LosAngelesTESRP.service
      
PartOf=vesta-nehm-LosAngelesTESRP.service
      
After=network.target remote-fs.target nss-lookup.target docker.service vesta-nehm-LosAngelesTESRP.service
      

      
[Install]
      
WantedBy=multi-user.target
      

      
[Service]
      
ExecStart=/opt/vesta/bin/service-wrapper vesta-neca-LosAngelesTESRP
      
Type=forking
      
KillMode=mixed
      
PIDFile=/var/run/vesta-neca-LosAngelesTESRP.pid
      
ExecStop=/usr/bin/docker stop vesta-neca-LosAngelesTESRP
      
RestartSec=30
      
Restart=always
      
StartLimitInterval=600
      
StartLimitBurst=3


      container3 which has issue



      [Unit]
      
Description=Proxy service for LosAngelesTESRP
      
BindsTo=vesta-neca-LosAngelesTESRP.service
      
PartOf=vesta-neca-LosAngelesTESRP.service
      
After=network.target network-interface-LosAngelesTESRP.service remote-fs.target nss-lookup.target docker.service vesta-neca-LosAngelesTESRP.service
      

      
[Install]
      
WantedBy=multi-user.target
      

      
[Service]
      
ExecStart=/opt/vesta/bin/service-wrapper vesta-proxy-LosAngelesTESRP
      
Type=forking
      
KillMode=mixed
      
PIDFile=/var/run/vesta-proxy-LosAngelesTESRP.pid
      
ExecStop=/usr/bin/docker stop vesta-proxy-LosAngelesTESRP
      
RestartSec=30
      

      
Restart=always
      
StartLimitInterval=600
      
StartLimitBurst=3
      





      
[root@services-2 system]# systemctl status vesta-proxy-LosAngelesTESRP.service
      
● vesta-proxy-LosAngelesTESRP.service - Proxy service for LosAngelesTESRP
      
   Loaded: loaded (/etc/systemd/system/vesta-proxy-LosAngelesTESRP.service; disabled; vendor preset: disabled)
      
   Active: inactive (dead) since Wed 2018-12-19 10:05:48 PST; 1h 19min ago
      
  Process: 2763 ExecStop=/usr/bin/docker stop vesta-proxy-LosAngelesTESRP (code=exited, status=0/SUCCESS)
      
  Process: 2533 ExecStart=/opt/vesta/bin/service-wrapper vesta-proxy-LosAngelesTESRP (code=exited, status=0/SUCCESS)
      
 Main PID: 2559
      

      
Dec 19 10:05:47 services-2.amber.lab systemd[1]: Installed new job vesta-proxy-LosAngelesTESRP.service/stop as 18224
      
Dec 19 10:05:47 services-2.amber.lab systemd[2763]: Executing: /usr/bin/docker stop vesta-proxy-LosAngelesTESRP
      
Dec 19 10:05:48 services-2.amber.lab docker[2763]: vesta-proxy-LosAngelesTESRP
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: Child 2763 belongs to vesta-proxy-LosAngelesTESRP.service
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service: control process exited, code=exited status=0
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service got final SIGCHLD for state stop
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service changed stop -> dead
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: Job vesta-proxy-LosAngelesTESRP.service/stop finished, result=done
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: Stopped Proxy service for LosAngelesTESRP.
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service: cgroup is empty





      systemd







      share|improve this question















      I have 3 docker containers whose unit files are as below. Autorestart works for 1st and 2nd in the dependency chain but doesnot work for last. I replaced docker containers with some test bash scripts with same relationships and autorestart seem to work fine. So it is issue with auto restart with docker container on the edge(edge case). The issue is important because we cannot automatically recover after last container crashes for some reason.



      container1(nehm) -> container 2(neca) > container 3(proxy)



      container1



      [Unit]
      
Description=NEHM service for LosAngelesTESRP
      
Requires=cassandra.service rabbitmq.service consul.service vesta-neca-LosAngelesTESRP.service
      
BindsTo=cassandra.service rabbitmq.service consul.service vesta-neca-LosAngelesTESRP.service
      
After=network.target remote-fs.target nss-lookup.target docker.service cassandra.service rabbitmq.service consul.service
      

      
[Install]
      
WantedBy=multi-user.target
      

      
[Service]
      
ExecStart=/opt/vesta/bin/service-wrapper vesta-nehm-LosAngelesTESRP
      
Type=forking
      
KillMode=mixed
      
PIDFile=/var/run/vesta-nehm-LosAngelesTESRP.pid
      
ExecStartPre=/bin/sh /etc/vesta/network/LosAngelesTESRP start
      
ExecStop=/usr/bin/docker stop vesta-nehm-LosAngelesTESRP
      
ExecStopPost=/bin/sh /etc/vesta/network/LosAngelesTESRP stop
      
RestartSec=30
      
Restart=always
      
StartLimitInterval=600
      
StartLimitBurst=3


      container2



      [Unit]
      
Description=neca service for LosAngelesTESRP
      
Requires=vesta-proxy-LosAngelesTESRP.service
      
BindsTo=vesta-nehm-LosAngelesTESRP.service vesta-proxy-LosAngelesTESRP.service
      
PartOf=vesta-nehm-LosAngelesTESRP.service
      
After=network.target remote-fs.target nss-lookup.target docker.service vesta-nehm-LosAngelesTESRP.service
      

      
[Install]
      
WantedBy=multi-user.target
      

      
[Service]
      
ExecStart=/opt/vesta/bin/service-wrapper vesta-neca-LosAngelesTESRP
      
Type=forking
      
KillMode=mixed
      
PIDFile=/var/run/vesta-neca-LosAngelesTESRP.pid
      
ExecStop=/usr/bin/docker stop vesta-neca-LosAngelesTESRP
      
RestartSec=30
      
Restart=always
      
StartLimitInterval=600
      
StartLimitBurst=3


      container3 which has issue



      [Unit]
      
Description=Proxy service for LosAngelesTESRP
      
BindsTo=vesta-neca-LosAngelesTESRP.service
      
PartOf=vesta-neca-LosAngelesTESRP.service
      
After=network.target network-interface-LosAngelesTESRP.service remote-fs.target nss-lookup.target docker.service vesta-neca-LosAngelesTESRP.service
      

      
[Install]
      
WantedBy=multi-user.target
      

      
[Service]
      
ExecStart=/opt/vesta/bin/service-wrapper vesta-proxy-LosAngelesTESRP
      
Type=forking
      
KillMode=mixed
      
PIDFile=/var/run/vesta-proxy-LosAngelesTESRP.pid
      
ExecStop=/usr/bin/docker stop vesta-proxy-LosAngelesTESRP
      
RestartSec=30
      

      
Restart=always
      
StartLimitInterval=600
      
StartLimitBurst=3
      





      
[root@services-2 system]# systemctl status vesta-proxy-LosAngelesTESRP.service
      
● vesta-proxy-LosAngelesTESRP.service - Proxy service for LosAngelesTESRP
      
   Loaded: loaded (/etc/systemd/system/vesta-proxy-LosAngelesTESRP.service; disabled; vendor preset: disabled)
      
   Active: inactive (dead) since Wed 2018-12-19 10:05:48 PST; 1h 19min ago
      
  Process: 2763 ExecStop=/usr/bin/docker stop vesta-proxy-LosAngelesTESRP (code=exited, status=0/SUCCESS)
      
  Process: 2533 ExecStart=/opt/vesta/bin/service-wrapper vesta-proxy-LosAngelesTESRP (code=exited, status=0/SUCCESS)
      
 Main PID: 2559
      

      
Dec 19 10:05:47 services-2.amber.lab systemd[1]: Installed new job vesta-proxy-LosAngelesTESRP.service/stop as 18224
      
Dec 19 10:05:47 services-2.amber.lab systemd[2763]: Executing: /usr/bin/docker stop vesta-proxy-LosAngelesTESRP
      
Dec 19 10:05:48 services-2.amber.lab docker[2763]: vesta-proxy-LosAngelesTESRP
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: Child 2763 belongs to vesta-proxy-LosAngelesTESRP.service
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service: control process exited, code=exited status=0
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service got final SIGCHLD for state stop
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service changed stop -> dead
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: Job vesta-proxy-LosAngelesTESRP.service/stop finished, result=done
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: Stopped Proxy service for LosAngelesTESRP.
      
Dec 19 10:05:48 services-2.amber.lab systemd[1]: vesta-proxy-LosAngelesTESRP.service: cgroup is empty





      systemd




      systemd






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 19 '18 at 20:53









      Rui F Ribeiro

      39k1479130




      39k1479130










      asked Dec 19 '18 at 19:28









      Roshan Lopes

      61




      61



























          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489990%2fsystemd-not-autorestarting-the-last-docker-container-after-it-crashes-or-kill-9%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489990%2fsystemd-not-autorestarting-the-last-docker-container-after-it-crashes-or-kill-9%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -

          Popular posts from this blog

          Morgemoulin

          Image
          Morgemoulin — miejscowość i gmina — Państwo   Francja Region Grand Est Departament Moza Okręg Verdun Kod INSEE 55357 Powierzchnia 6,82 km² Populacja  (1990) • liczba ludności 75 • gęstość 11 os./km² Kod pocztowy 55400 Położenie na mapie Francji Morgemoulin 49°14′N   5°35′E / 49,233333   5,583333 Portal Francja Morgemoulin – miejscowość i gmina we Francji, w regionie Grand Est, w departamencie Moza. Według danych na rok 1990 gminę zamieszkiwało 75 osób, a gęstość zaludnienia wynosiła 11 osób/km² (wśród 2335 gmin Lotaryngii Morgemoulin plasuje się na 970. miejscu pod względem liczby ludności, natomiast pod względem powierzchni na miejscu 848.). Bibliografia | Francuski urząd statystyczny ( fr. ) . p   •   d   •   e Gminy okręgu Verdun Abaucourt-Hautecourt • Aincreville • Ambly-sur-Meuse • Amel-sur-l'Étang • Ancemont • Arrancy-sur-Crusne • Aubréville • Autré...
          Read more

          Scott Moir

          Image
          Scott Moir Tessa Virtue i Scott Moir w 2016 r. Reprezentacja   Kanada Data i miejsce urodzenia 2 września 1987 London Wzrost 180 cm Konkurencja Pary taneczne Partner sportowy Tessa Virtue Trener Marie-France Dubreuil, Patrice Lauzon, Romain Haguenauer Poprzednio: Marina Zujewa, Oleg Epstein, Igor Szpilband, Johnny Johns, Carol Moir, Paul MacIntosh, Suzanne Killing Klub Montreal International School of Skating Poprzednio: Arctic Edge FSC Ilderton Skating Club Lokalizacja treningowa Montreal Poprzednio: Canton Kitchener Rekordy życiowe ISU przed sezonem 2018/2019 Nota łączna 206,07 Igrzyska Olimpijskie 2018 Taniec krótki 83,67 Igrzyska Olimpijskie 2018 Taniec dowolny 122,40 Igrzyska Olimpijskie 2018 Dorobek medalowy Reprezentacja   Kanada Igrzyska olimpijskie Złoto Vancouver 2010 pary taneczne Złoto Pjongczang 2018 pary taneczne Złoto Pjongczang 2018 drużynowo Srebro S...
          Read more

          Souastre

          Image
          Souastre — miejscowość i gmina — Herb Państwo   Francja Region Hauts-de-France Departament Pas-de-Calais Okręg Arras Kod INSEE 62800 Powierzchnia 7,18 km² Populacja  (1990) • liczba ludności 352 • gęstość 49 os./km² Kod pocztowy 62111 Położenie na mapie Francji Souastre 50°09′N   2°34′E / 50,150000   2,566667 Portal Francja Souastre – miejscowość i gmina we Francji, w regionie Hauts-de-France, w departamencie Pas-de-Calais. Według danych na rok 1990 gminę zamieszkiwały 352 osoby, a gęstość zaludnienia wynosiła 49 osób/km² (wśród 1549 gmin regionu Nord-Pas-de-Calais Souastre plasuje się na 887. miejscu pod względem liczby ludności, natomiast pod względem powierzchni na miejscu 507.). Bibliografia | Francuski urząd statystyczny ( fr. ) . p   •   d   •   e Gminy okręgu Arras Ablain-Saint-Nazaire Ablainzevelle Acheville Achicourt Achiet-le-Grand Achiet-le-Pe...
          Read more