Hi, based on the documentation and the “ cron-example ” project, I thought that if I just added a similar line to my dockerfile, I’d be in business. However, my container can’t find crontab Connecting to 150deeb26a5b3d03c15f8bc1c64e0c8d... Spawning shell... root@150deeb:/usr/src/app# crontab bash: cr…

Hey @aka this is really strange, as I just built your project successfully (with the crontab reference) for a raspberry pi application. What device type are you building for? Perhaps one of our base images has been built in an odd way that we haven’t noticed yet.

Hi Cameron, I’m glad to hear it built! This is the same hardware (two Beaglebones Black) as another issue you helped with this morning: Can't find crontab or systemctl in Beaglebone debian image, what am I doing wrong? …so I bet the container process is messing up (probably because of something I …

Hey @aka , can you tell us what is the base image you are using? The INITSYSTEM variable only has effect in the resin/... base images maintained by us, as much as I know, and almost all of them include systemd. If we may, it would be great to look at your Dockerfile or Dockerfile.template, and any …

Sure, I’m using Beaglebone Black’s Debian image (or trying to)… # base-image for python on any machine using a template variable, # see more about dockerfile templates here:http://docs.resin.io/pages/deployment/docker-templates FROM resin/%%RESIN_MACHINE_NAME%%-debian # RUN apt-get update && apt-g…

Looks like you need to install the cron package explicitly, seems like with that change it works. Can you please try that? Also, an idea, since you have initsystem enabled, an alternative is using systemd timers instead of cron, described e.g. here https://wiki.archlinux.org/index.php/Systemd/Timer…

Thanks for the reply! In th first post you can see that systemctl / systemd is also missing. I’d like to figure out why the base image isn’t behaving as expected, rather than manually install stuff that’s supposed to come with Debian…I think it’s an indicator something more substantial is messed-up…

What do you get if you just add cron \ to the list of packages required in the dockerfile? That may well solve for the immediate problem, whilst we look at the base image.

As a colleague of mine has just pointed out, the following line in the dockerfile tidies the package lists from the build, as there’s no need for that to be deployed to every device in a fleet once the container is built with the correct packages. [image] aka: apt-get clean && rm -rf /var/lib/a…

Thanks for the replies! Adding cron and systemd to the list of required packages works well once you delete the apt-get clean && rm -rf /var/lib/apt/lists/* stuff… Weirdly, the CMD still isn’t running properly once the container starts. I reproduced this on another Beaglebone Black here, just in ca…

Hmmm, now with cron and systemd installed via the Dockerfile, I’m seeing this error on both Beaglebones: 27.03.18 12:07:43 (-0400) Systemd init system enabled. 27.03.18 12:07:44 (-0400) Failed to insert module 'kdbus': Function notimplemented 27.03.18 12:07:44 (-0400) systemd 230 running in syste…

Can't find crontab or systemctl in Beaglebone debian image, what am I doing wrong?

Product support

esetnik July 31, 2018, 3:44pm 23

Might be the same thing as The "Failed to install release agent" bug is back

Topic		Replies	Views
Docker run arguments Product support	25	2286	August 23, 2019
`env INITSYSTEM on` not working Product support systemd	16	3199	August 1, 2019
Container fails to start - "failed to attach 1 to compat systemd cgroup" balenaOS	40	6383	September 22, 2019
Systemd not available within container despite INITSYSTEM on balenaEngine raspberrypi3 , systemd , dockerfile	4	1834	April 9, 2019
Get systemd installed in a Balena image balenaEngine support , docker	31	2812	May 12, 2020

Can't find crontab or systemctl in Beaglebone debian image, what am I doing wrong?

Related topics