I have the following in my |config.yml|: |# Ensure docker starts automatically instead of being socket-activated systemd: units: - name: docker.service enabled: true |
However, after the system starts: |$ systemctl status docker.service ● docker.service - Docker Application Container Engine Loaded: loaded (/run/systemd/system/docker.service; disabled; vendor preset: enabled) | and the daemon is still socket activated, ie it doesn’t start until I make a request such as |docker ps|. Any containers with |restart: always| don’t start until I ssh in and do |docker ps|. The rest of my |config.yml| is acted on successfully, and the |systemd| section is at the end. |journalctl --identifier=ignition --all| shows this: |ignition[422]: files: op(4): [finished] processing unit "etcd-member.service" ignition[422]: files: the enable field has been deprecated in favor of enabled ignition[422]: files: op(6): [started] enabling unit "etcd-member.service" ignition[422]: files: op(6): [finished] enabling unit "etcd-member.service" ignition[422]: files: op(7): [started] processing unit "docker.service" ignition[422]: files: op(7): [finished] processing unit "docker.service" ignition[422]: files: op(8): [started] enabling unit "docker.service" ignition[422]: files: op(8): [finished] enabling unit "docker.service" | Any idea why this isn’t taking effect? -- You received this message because you are subscribed to the Google Groups "CoreOS Dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/coreos-dev/7d467331-d014-62e0-e3b5-cf1908d8269c%40kerith.ca.
