Git Product home page Git Product logo

deftwork / samba Goto Github PK

View Code? Open in Web Editor NEW
69.0 7.0 36.0 36 KB

A Dockerfile to build multi-architecture images of Samba, which is the standard Windows interoperability suite of programs for Linux and Unix. This is my personal docker recipe.

Home Page: https://deft.work/samba

License: MIT License

Dockerfile 12.19% Makefile 25.94% Shell 61.87%
samba samba-server multi-platform multi-arch docker

samba's Introduction

Samba

A Docker file to build images for many platforms (linux/amd64, linux/arm64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6) with a installation of Samba that is the standard Windows interoperability suite of programs for Linux and Unix. This is my own Multi-architecture docker recipe.

Be aware! You should read carefully the usage documentation of every tool!

Thanks to

Details

Website GitHub Docker Hub
Deft.Work my personal blog Samba Samba
Docker Pulls Docker Stars Size Sponsors
Docker pulls Docker stars Docker Image size GitHub Sponsors

Compatible Architectures

This image has been builded using buildx for this architectures:

  • amd64 arm64 ppc64le s390x 386 arm/v7 arm/v6

Usage

I use it to share files between Linux and Windows, but Samba has many other capabilities.

ATTENTION: This is a recipe highly adapted to my needs, it might not fit yours. Deal with local filesystem permissions, container permissions and Samba permissions is a Hell, so I've made a workarround to keep things as simple as possible. I want avoid that the usage of this conainer would affect current file permisions of my local system, so, I've "synchronized" the owner of the path to be shared with Samba user. This mean that some commitments and limitations must be assumed.

Container will be configured as samba sharing server and it just needs:

  • host directories to be mounted,
  • users (one or more uid:gid:username:usergroup:password tuples) provided,
  • shares defined (name, path, users).

-u uid:gid:username:usergroup:password

  • uid from user p.e. 1000
  • gid from group that user belong p.e. 1000
  • username p.e. alice
  • usergroup (the one to whom user belongs) p.e. alice
  • password (The password may be different from the user's actual password from your host filesystem)

-s name:path:rw:user1[,user2[,userN]]

  • add share, that is visible as 'name', exposing contents of 'path' directory for read+write (rw) or read-only (ro) access for specified logins user1, user2, .., userN

Serve

Start a samba fileshare.

docker run -d -p 139:139 -p 445:445 \
  -- hostname any-host-name \ # Optional
  -e TZ=Europe/Madrid \ # Optional
  -v /any/path:/share/data \ # Replace /any/path with some path in your system owned by a real user from your host filesystem
  elswork/samba \
  -u "1000:1000:alice:alice:put-any-password-here" \ # At least the first user must match (password can be different) with a real user from your host filesystem
  -u "1001:1001:bob:bob:secret" \
  -u "1002:1002:guest:guest:guest" \
  -s "Backup directory:/share/backups:rw:alice,bob" \ 
  -s "Alice (private):/share/data/alice:rw:alice" \
  -s "Bob (private):/share/data/bob:rw:bob" \
  -s "Documents (readonly):/share/data/documents:ro:guest,alice,bob"

This is my real usage command:

docker run -d -p 139:139 -p 445:445 -e TZ=Europe/Madrid \
    -v /home/pirate/docker/makefile:/share/folder elswork/samba \
    -u "1000:1000:pirate:pirate:put-any-password-here" \
    -s "SmbShare:/share/folder:rw:pirate"

or this if the user that owns the path to be shared match with the user that raise up the container:

docker run -d -p 139:139 -p 445:445 --hostname $HOSTNAME -e TZ=Europe/Madrid \
    -v /home/pirate/docker/makefile:/share/folder elswork/samba \
    -u "$(id -u):$(id -g):$(id -un):$(id -gn):put-any-password-here" \
    -s "SmbShare:/share/folder:rw:$(id -un)"

On Windows point your filebrowser to \\host-ip\ to preview site.


Sponsor me! Together we will be unstoppable.

Other ways to fund me:

GitHub Sponsors Donate PayPal Donate with Bitcoin Donate with Ethereum

samba's People

Contributors

144992 avatar andriimartynov avatar elswork avatar forbish avatar ngosang avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

samba's Issues

When using rootless Docker, the file owner is a non-existing user

Hi,

I'm using Docker rootless mode and running elswork/samba by using this docker-compose.yml file:

services:
  samba:
    container_name: samba
    image: elswork/samba
    env_file:
      - .env
    ports:
      - "139:139"
      - "445:445"
    volumes:
      - ./backups:/share/backups
    command:
      - -u1000:1000:myuser:myuser:mypassword
      - -sBackups:/share/backups:rw:myuser
    restart: always

However, when I tried to create a file from Windows, this error message appears:

image

I had to run chmod 777 backups to be able to create files. When I inspect the created file, the user is 100999:100999:

-rwxr--r-- 1 100999 100999    0 Apr 13 01:02 'New Text Document.txt'

Is this normal behavior, or is it due to the fact that I'm in rootless mode?

Thanks.

Hub Docker date problem on Raspberry pi 4

Hi,

I use Raspberry pi 4 and my docker-compose was :

image: elswork/samba

Because of fail to login, I see the log (syslog) STATUS_INVALID_LOGON_HOURS. I entered sudo docker-compose exec samba date and seen Mon Jun 15 16:41:36 CEST 2071

The date is incorrect because we will not be in life in 2071 (planet destroyed).

I builded on my own (with alpine 3.12 because alpine is KO from 3.13 on raspberry) :

    build:
      context: https://github.com/deftwork/samba.git
      args:
        BASEIMAGE: alpine:3.12

And the date is correct and the login works.

FYI :)

Regards,

Add user 'xxxx' addgroup: group 'xxxx' in use

If I start the container using docker run ... everything works fine. If I then stop and restart the container, I get

Add user 'xxxx' addgroup: group 'xxxx' in use

a couple times and the container quits. Could this be caused by the variable FIRSTTIME in entrypoint to not being stored in the container?
Am I doing anything wrong?

Update dependencies in Docker image

I was doing a security scanner using Grype => https://github.com/anchore/grype
And I detected your Docker image has some outdated dependencies. I don't think they are a security risk but it's a good practice to publish releases more often. Thank you for your work!

grype elswork/samba:4.15.7 --only-fixed | grep -i -E '(High|Critical)'

Docker image: elswork/samba:4.15.7
cups-libs                 2.4.2-r0          2.4.2-r2          apk   CVE-2023-34241  High      
expat                     2.4.8-r0          2.6.0-r0          apk   CVE-2023-52425  High      
expat                     2.4.8-r0          2.5.0-r0          apk   CVE-2022-43680  High      
expat                     2.4.8-r0          2.4.9-r0          apk   CVE-2022-40674  High      
gnutls                    3.7.7-r0          3.7.7-r1          apk   CVE-2023-0361   High      
libarchive                3.6.1-r0          3.6.1-r1          apk   CVE-2022-36227  Critical  
libcap                    2.64-r0           2.64-r1           apk   CVE-2023-2603   High      
libcrypto1.1              1.1.1q-r0         1.1.1t-r1         apk   CVE-2023-0464   High      
libcrypto1.1              1.1.1q-r0         1.1.1t-r0         apk   CVE-2023-0286   High      
libcrypto1.1              1.1.1q-r0         1.1.1t-r0         apk   CVE-2023-0215   High      
libcrypto1.1              1.1.1q-r0         1.1.1t-r0         apk   CVE-2022-4450   High      
libsmbclient              4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
libsmbclient              4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
libsmbclient              4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
libsmbclient              4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
libsmbclient              4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
libsmbclient              4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
libsmbclient              4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
libsmbclient              4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
libsmbclient              4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
libsmbclient              4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
libssl1.1                 1.1.1q-r0         1.1.1t-r1         apk   CVE-2023-0464   High      
libssl1.1                 1.1.1q-r0         1.1.1t-r0         apk   CVE-2023-0286   High      
libssl1.1                 1.1.1q-r0         1.1.1t-r0         apk   CVE-2023-0215   High      
libssl1.1                 1.1.1q-r0         1.1.1t-r0         apk   CVE-2022-4450   High      
libtasn1                  4.18.0-r0         4.18.0-r1         apk   CVE-2021-46848  Critical  
libwbclient               4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
libwbclient               4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
libwbclient               4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
libwbclient               4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
libwbclient               4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
libwbclient               4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
libwbclient               4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
libwbclient               4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
libwbclient               4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
libwbclient               4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
ncurses-libs              6.3_p20220521-r0  6.3_p20220521-r1  apk   CVE-2023-29491  High      
ncurses-terminfo-base     6.3_p20220521-r0  6.3_p20220521-r1  apk   CVE-2023-29491  High      
samba                     4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
samba                     4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
samba                     4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
samba                     4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
samba                     4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
samba                     4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
samba                     4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
samba                     4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
samba                     4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
samba                     4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
samba-client              4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
samba-client              4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
samba-client              4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
samba-client              4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
samba-client              4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
samba-client              4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
samba-client              4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
samba-client              4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
samba-client              4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
samba-client              4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
samba-client-libs         4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
samba-client-libs         4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
samba-client-libs         4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
samba-client-libs         4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
samba-client-libs         4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
samba-client-libs         4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
samba-client-libs         4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
samba-client-libs         4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
samba-client-libs         4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
samba-client-libs         4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
samba-common              4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
samba-common              4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
samba-common              4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
samba-common              4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
samba-common              4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
samba-common              4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
samba-common              4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
samba-common              4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
samba-common              4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
samba-common              4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
samba-common-server-libs  4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
samba-common-server-libs  4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
samba-common-server-libs  4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
samba-common-server-libs  4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
samba-common-server-libs  4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
samba-common-server-libs  4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
samba-common-server-libs  4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
samba-common-server-libs  4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
samba-common-server-libs  4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
samba-common-server-libs  4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
samba-common-tools        4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
samba-common-tools        4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
samba-common-tools        4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
samba-common-tools        4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
samba-common-tools        4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
samba-common-tools        4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
samba-common-tools        4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
samba-common-tools        4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
samba-common-tools        4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
samba-common-tools        4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
samba-libs                4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
samba-libs                4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
samba-libs                4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
samba-libs                4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
samba-libs                4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
samba-libs                4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
samba-libs                4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
samba-libs                4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
samba-libs                4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
samba-libs                4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
samba-server              4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
samba-server              4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
samba-server              4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
samba-server              4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
samba-server              4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
samba-server              4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
samba-server              4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
samba-server              4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
samba-server              4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
samba-server              4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      
samba-util-libs           4.15.7-r0         4.15.13-r0        apk   CVE-2022-45141  Critical  
samba-util-libs           4.15.7-r0         4.15.12-r0        apk   CVE-2022-42898  High      
samba-util-libs           4.15.7-r0         4.15.13-r0        apk   CVE-2022-38023  High      
samba-util-libs           4.15.7-r0         4.15.13-r0        apk   CVE-2022-37967  High      
samba-util-libs           4.15.7-r0         4.15.13-r0        apk   CVE-2022-37966  High      
samba-util-libs           4.15.7-r0         4.15.12-r0        apk   CVE-2022-32745  High      
samba-util-libs           4.15.7-r0         4.15.12-r0        apk   CVE-2022-32744  High      
samba-util-libs           4.15.7-r0         4.15.12-r0        apk   CVE-2022-2031   High      
samba-util-libs           4.15.7-r0         4.15.12-r0        apk   CVE-2022-0336   High      
samba-util-libs           4.15.7-r0         4.15.12-r0        apk   CVE-2021-44142  High      

Remove password from logs

Hello, I noticed password of the configured share is being written to logs. Can you please remove this log statement as it is a security risk?

And thanks a lot for creating this! Helped me a ton for my home lab use.

ro access

Hi deftwork! How are you?
Is it possible that by specifying a type of ro permission on a shared folder, the user can still edit the content? It's like doesn't take the read-only permission I'm giving it.
Thanks, regards.

Please add a docker-compose example in the readme

I use your docker on my pi4. great job !
But i lose some time to find the best configuration for my docker compose. I purpose you an example that can be useful :)

version: '3.7'
networks: 
internal:
samba:
    image: elswork/samba
    container_name: samba
    hostname: samba
    networks: 
        - internal
    ports:
        - 139:139
        - 445:445
    volumes:
        - /MY/LOCAL/SHARED:/shared
    command: '-u "myuser:abetterpasswd" -s "SHARED:/shared:rw:myuser"'

for smb://your-host/shared

network speed this image.

Good afternoon, I use this image but I ran into a network speed problem.
the speed is more than 11MB\s does not rise, although I use a gigabit network.
other images do not have this problem.
what can you suggest?

Client: Docker Engine - Community
Version: 20.10.14
API version: 1.41
Go version: go1.16.15
Git commit: a224086
Built: Thu Mar 24 01:48:02 2022
OS/Arch: linux/amd64
Context: default

Image version is : 4.15.5

Possible permissions problem and home user directory

I have 2 folders /data/homer and /data/home-assistant. Both the folders and their content are owned by user victor and group victor. The permissions for the contents of the data folder is rw-rw-r-- or 664. I want to share the /data folder, but login with custom credentials. So I have the following docker command:

docker run -d -p 139:139 -p 445:445 \
  --hostname $HOSTNAME \
  -e TZ=Europe/Paris \
  -v /data:/data \
  elswork/samba \
  -u "1000:1000:victor:victor:RaNdOmPaSwOrD" \ # An existing user and group on my host filesystem, but a made up password
  -u "1001:1001:bob:bob:anotherpassword" \ # User and group does not exist on host filesystem, password is made up
  -s "Config:/data:rw:bob"

Some odd behaviour I don't understand:

  • When I log in as user victor I can view and edit the files, but when I log in as user bob I can only view the files.
    I tried to get both users in the same group, but the container does error out saying the group already exists.
    So victor: 1000:100:victor:users:RaNdOmPaSwOrD and bob: 1001:100:bob:users:anotherpassword - existing group on host filesystem. I also did recursive chown to the /data folder for this test.
    How do I also get bob to be able to edit files?
  • I also noticed if I log in with victor I also get a folder called victor, and for bob I get a folder called bob. I assume this is the user home directory which is set to not browsable in /etc/samba/smb.conf.
    When I commented out the [homes] share from this file the user directory was gone. Is this something you can change?
    image

Error after restarting Docker container

image: elswork/samba:3.2.8
command: '-u 1001:1001:fake_user:fake_group:fake_password'
restart: unless-stopped

The first time I run the Docker container it works fine. If I restart the container, it keeps restarting forever with an error. The only fix is to remove the container and start again. That mean I can not restart my server because samba stops working.

First start:

Add user 'fake_user' with password 'fake_password' Added user fake_user.,
DONE,
smbd version 4.14.5 started.,
Copyright Andrew Tridgell and the Samba Team 1992-2021,
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections,

After manual restart or system reboot:

addgroup: group 'fake_group' in use,
Add user 'fake_user' $addgroup: group 'fake_group' in use,
Add user 'fake_user' $addgroup: group 'fake_group' in use,
Add user 'fake_user' $addgroup: group 'fake_group' in use,

Not accessible

No shares are accessible or visible. If I enter \IP I get and open folder dialog and it says \IP is not accessible. You might not have permission to use this network resource......

If I enter \IP\Sharefolder I get Windows cannot access \IP\Sharefolder.

Logs says the user was created and the share was created. I can use bash and see the files are accessible in the container.

created using

docker run -d -p 139:139 -p 445:445 --hostname aaa
-e TZ=xxx --name samba
-v /data01:/opt elswork/samba
-u "1000:1000:noob:noob:password"
-s "Sharefolder:/opt:rw:noob"

I've done both
sudo chown -R 1000:1000 data01/
sudo chmod -R 777 data01/

But I should see the folder at least even if I can't access it.

Follow symbolic links

Hi, thanks for creating this fantastic image.
Still a request, is it possible to implement "follow symlinks = yes", so symbolic links are visable in the shares?
Thanks in advanced.

users don't have write rights :(

Hey folks,

I have a problem that all my users don't have write rights to the shares :(

So maybe I just don't understand correct how I have to create the users.
Is it mandatory that the user exists on the host with the same username and userid or is this just needed for the container?
Also the share on the host should have the same username/id as the owner of the directory or not?

docker run -d -p 445:445 \
  -- hostname any-host-name \ # Optional
  -e TZ=Europe/Madrid \ # Optional
  -v /any/path:/share/data \ # Replace /any/path with some path in your system owned by a real user from your host filesystem
  elswork/samba \
  -u "1000:1000:alice:alice:put-any-password-here" \ # At least the first user must match (password can be different) with a real user from your host filesystem
  -u "1001:1001:bob:bob:secret" \
  -u "1002:1002:guest:guest:guest" \
  -s "Backup directory:/share/backups:rw:alice,bob" \ 
  -s "Alice (private):/share/data/alice:rw:alice" \
  -s "Bob (private):/share/data/bob:rw:bob" \
  -s "Documents (readonly):/share/data/documents:ro:guest,alice,bob"

Vulnerabilities in Docker image elswork/samba:3.2.8

Docker image elswork/samba:3.2.8
https://github.com/anchore/grype

grype elswork/samba:3.2.8
 ✔ Vulnerability DB        [no update available]
 ✔ Loaded image            
 ✔ Parsed image            
 ✔ Cataloged packages      [61 packages]
 ✔ Scanned image           [17 vulnerabilities]
NAME                      INSTALLED  FIXED-IN  VULNERABILITY   SEVERITY 
cups-libs                 2.3.3-r4             CVE-2018-6553   High      
libarchive                3.5.2-r2             CVE-2021-36976  Medium    
libldap                   2.6.0-r0             CVE-2015-3276   Medium    
libsmbclient              4.15.2-r0            CVE-2011-2411   High      
libwbclient               4.15.2-r0            CVE-2011-2411   High      
lz4-libs                  1.9.3-r0   1.9.3-r1  CVE-2021-3520   Critical  
samba                     4.15.2-r0            CVE-2011-2411   High      
samba-client              4.15.2-r0            CVE-2011-2411   High      
samba-client-libs         4.15.2-r0            CVE-2011-2411   High      
samba-common              4.15.2-r0            CVE-2011-2411   High      
samba-common-server-libs  4.15.2-r0            CVE-2011-2411   High      
samba-common-tools        4.15.2-r0            CVE-2011-2411   High      
samba-libs                4.15.2-r0            CVE-2011-2411   High      
samba-server              4.15.2-r0            CVE-2007-2407   Medium    
samba-server              4.15.2-r0            CVE-2011-2411   High      
samba-util-libs           4.15.2-r0            CVE-2011-2411   High 

do_connect: Connection to localhost failed (Error NT_STATUS_IO_TIMEOUT)

I updated today and I am getting an error on the health check

do_connect: Connection to localhost failed (Error NT_STATUS_IO_TIMEOUT)

Host is RPi4.

Could be related to an issue with libseccomp2 that has affected other containers on RPi4.

https://github.com/visibilityspots/dockerfile-cloudflared/issues/30
https://github.com/alpinelinux/docker-alpine/issues/110

But I am not sure ... another symptom is the container doesn't have the correct date/time

bash-5.1# date
Sun Jan  0 00:100:4174038  1900

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.