Mount: permission denied on microservices applications

Product support
1

Hi,

I am using a microservices application, and I get the following error messages every time I connect (or restart) the device. Do you know what those error means? The error does not affect my services (all work fine!), but I do not understand the source of it.

Thanks!

hostname: you must be root to change the host name
27.02.18 18:40:13 (+0100)  SERVICE_NAME  mount: permission denied
27.02.18 18:40:13 (+0100)  SERVICE_NAME  mount: permission denied
27.02.18 18:40:13 (+0100)  SERVICE_NAME  mount: permission denied
27.02.18 18:40:13 (+0100)  SERVICE_NAME  mount: permission denied
27.02.18 18:40:13 (+0100)  SERVICE_NAME  mount: mount point /tmp/console is not a directory
27.02.18 18:40:13 (+0100)  SERVICE_NAME  umount: /dev: must be superuser to unmount
27.02.18 18:40:13 (+0100)  SERVICE_NAME  mount: permission denied
27.02.18 18:40:13 (+0100)  SERVICE_NAME  mount: permission denied
27.02.18 18:40:13 (+0100)  SERVICE_NAME  /sbin/udevd
6

Hi. Can you tell us what base images are you using?

8

It looks like this has been fixed in the base images at the newest date tag. Can you change your base images to the latest date tag and let us know if you still see these warnings?

10

I am using the docker base image resin/raspberrypi3-python:3.6-slim. I will try updating first such image. I’ll keep you noticed.

Thank you for your fast response!

11

Sorry for the long delay. I wanted to be sure that I successfully updated the docker base images.

I am using resin/raspberrypi3-python:3.6-slim-20180401. The error has been solved. It just prints now:

hostname: you must be root to change the host name 04.04.18 10:22:21 (+0200)
service-name /sbin/udevd

Thank you.

12

You are welcome. Glad it’s working for you now

13

I’m having the same issue as OP using resin/raspberrypi3-openjdk:8-jre

19.05.18 09:12:05 (+0200) Starting service 'SERVICE_NAME sha256:d03f0a631b2ae3587eb16f14dac6634dd0d58ffd4170be9c892c3201cb4c252f'
19.05.18 09:12:06 (+0200)  SERVICE_NAME  hostname: you must be root to change the host name
19.05.18 09:12:06 (+0200)  SERVICE_NAME  mount: permission denied
19.05.18 09:12:06 (+0200) Started service 'SERVICE_NAME  sha256:d03f0a631b2ae3587eb16f14dac6634dd0d58ffd4170be9c892c3201cb4c252f'
19.05.18 09:12:06 (+0200)  SERVICE_NAME  mount: permission denied
19.05.18 09:12:06 (+0200)  SERVICE_NAME mount: permission denied
19.05.18 09:12:06 (+0200)  SERVICE_NAME mount: permission denied
19.05.18 09:12:06 (+0200)  SERVICE_NAME mount: mount point /tmp/console is not a directory
19.05.18 09:12:06 (+0200)  SERVICE_NAME umount: /dev: must be superuser to unmount
19.05.18 09:12:06 (+0200)  SERVICE_NAME mount: permission denied
19.05.18 09:12:06 (+0200)  SERVICE_NAME mount: permission denied
19.05.18 09:12:06 (+0200)  SERVICE_NAME /sbin/udevd

I’m using a multicontainer set-up, and the possibly-relevant parts of docker-compose.yml are:

version: '2'
services:
  SERVICE_NAME:
    restart: always
    build: ./SERVICE_NAME
    expose:
      - "8081"
18

Hi @martenjacobs,

This issue should be fixed now in resin/raspberrypi3-openjdk:8-jre as well.

19

I’m seeing the same error. It is affecting my ability to create a 4th container riffing off (very well constructed, I should mention) multi-container starter. Here’s what I did:

  • Add a 4th service based off of the debian:stretch and node:7-slim base images (tried both).
  • Pushed up to resin dashboard, saw the new service appear but it never fully starts, won’t get a shell.

The CMD in the service’s Dockerfile is ["echo", "it works"] and that’s pretty much it.

I’m not sure what the issue is. I’m open to ideas. If a reduced test case is desirable I can produce the code.

27

Hi @balibebas,

A minimal test case would be very helpful indeed - are you still having this issue?