Apollo: chown: invalid user: 'my_name:my_name'

Created on 1 Apr 2019 · 5Comments · Source: ApolloAuto/apollo

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.

System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04): 16.04
Apollo installed from (source or binary): Source
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0): 3.5

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:
Issue : I have installed some packages in the docker and committed the image so that I can use the same image for future use. However when I try to load the local image I am facing the below error. Could you please let me know the fix for this.

[INFO] *********************apollo new image is built*******************
addgroup: The GID `1001' is already in use.
usermod: user 'my_name' does not exist
chown: invalid user: 'my_name:my_name'
[ OK ] Finished setting up Apollo docker environment. Now you can enter with: 
bash docker/scripts/dev_into.sh
[ OK ] Enjoy!

Though it says Now you can enter with: bash docker/scripts/dev_into.sh when I try it I am getting the below error:

unable to find user my_name: no matching entries in passwd file

Supporting materials (screenshots, command lines, code/script snippets):

Docker Help wanted

Source

kk2491

Most helpful comment

Hi @kk2491 , you are supposed to build docker image from Dockerfile instead of docker commit in a running container.
scripts/docker_adduser.sh will setup the container accordingly. So if you bring up a container from a customized container, this script runs twice which causes conflict and failure.

xiaoxq on 2 Apr 2019

👍3

All 5 comments

@kk2491 have you installed Docker using our recommended process? Also are you building directly as root?
Another recommendation is that I think you have to remove all containers and images and also grant the correct permissions. Let me know if these help.

natashadsouza on 1 Apr 2019

@natashadsouza Thanks for the response.

Yes, I have installed the docker using the recommended process. And I am able to dev_start.sh without any issues, if I use the default images. Issue occurs if I use the custom docker image which is locally saved.

Thank you,
KK

kk2491 on 2 Apr 2019