xiaodongjie

and to you, too.

@Rinzwind o/ Thank you.

Merry Christmas!

Hello folks.

It seems to be a crown.

@hg8 :)

:) Long time no see folks o/

@cl-netbox yeah, very pleasure.

:D hat make us very pleasure.

@cl-netbox you're welcome

I like your answers.

+20

@cl-netbox yes, just now i saw them.

:D

@cl-netbox right. from you.

@cl-netbox thank you, got new one.

@cl-netbox Good friend!, Did you give me an upvote for my last answer?

@cl-netbox Good morning :)

@StarOS yes, right.

Good Morning!

Hi, @A.B.

For UID

@Oli did you read last part of my answer?

@Oli right?

So It'll work on the both.

It'll show you as following in container.

And when you run $getfacl /incoming command on The container.

It'll show you as follow in host.

When you run $ getfacl /media/steve/incoming command,

And it will be parsed on the container.

Then it could not be parsed on host, but attribute will be written for the directory.

$ sudo setfacl -m u:33:rwx ... On the host.

then it'll work for host and

$ sudo setfacl -m u:www-data:rwx ... On the host.

For host's www-data

yes, right.

on the host,

Then

on the host, www-data's id is 100.

@Oli yes, right. but container knows it is www-data. For example, on the container, www-data's id is 33 and

second command should be used on host.

first command should be used on container.

for user id number rather than user name.

$ sudo setfacl -m u:<got_number_above>:rwx /media/steve/incoming

$ cat /etc/passwd | grep "^www-data:" | awk -F ":" '{print $3}'

@Oli I added some lines.

@Oli yeah, tested it.

Hi, @Oli