Samba docker by dlandon - Revision history

Adminguy: /* docker-compose.yml */

2020-08-12T04:12:18Z

docker-compose.yml

Adminguy: /* docker-compose.yml */

2020-08-12T04:11:15Z

docker-compose.yml

Adminguy at 04:10, 12 August 2020

2020-08-12T04:10:30Z

Adminguy at 04:10, 12 August 2020

2020-08-12T04:10:08Z

Adminguy at 04:09, 12 August 2020

2020-08-12T04:09:46Z

Adminguy at 04:08, 12 August 2020

2020-08-12T04:08:04Z

Adminguy: Created page with "This is currently the most popular Samba image for docker. Here are notes for reference."

2020-08-12T03:59:35Z

Created page with "This is currently the most popular Samba image for docker. Here are notes for reference."

New page

This is currently the most popular Samba image for docker. Here are notes for reference.

@@ Line 34: / Line 34: @@
 #        PERMISSIONS:
 #for further troubleshooting, download the git repo, and grep through the code.
-#another note: I had no issues doing samba shares, that were subfolders of a parent share.
+#note: I had no issues doing samba shares, that were subfolders of a parent share.
 </pre>

@@ Line 15: / Line 15: @@
        restart: always
        volumes:
-#watch out for semi-colons here between. must be colons NOT semi
+#watch out for semi-colons here between volumes. must be colons NOT semi
          - ./localdir/from/docker-compose/root/:/anydirectory/on/docker/container
        environment:
-#these are semi-colons in the user section
+#however, these are semi-colons in the user section
          USER:    username1;somepassword
          USER2:   username2;somepassword
@@ Line 36: / Line 36: @@
 #another note: I had no issues doing samba shares, that were subfolders of a parent share.
 </pre>
 ===usage===

@@ Line 43: / Line 43: @@
 Note that you use forward slashes in the terminal. In file explorer, you will need backslashes.
-==Parent Page==
+==Back to:==
 [[Docker]]

← Older revision		Revision as of 04:10, 12 August 2020
Line 42:		Line 42:

	Note that you use forward slashes in the terminal. In file explorer, you will need backslashes.		Note that you use forward slashes in the terminal. In file explorer, you will need backslashes.
		+
		+	==Parent Page==
		+	[[Docker]]

@@ Line 1: / Line 1: @@
 This is currently the most popular Samba image for docker. Here are notes for reference.
 <pre>
 version: '3'
@@ Line 35: / Line 36: @@
 #another note: I had no issues doing samba shares, that were subfolders of a parent share.
 </pre>

← Older revision		Revision as of 04:08, 12 August 2020
Line 1:		Line 1:
	This is currently the most popular Samba image for docker. Here are notes for reference.		This is currently the most popular Samba image for docker. Here are notes for reference.
		+
		+	<pre>
		+	version: '3'
		+
		+	services:
		+	samba_fileshare:
		+	image: dperson/samba
		+	container_name: samba_share
		+	ports:
		+	- 139:139
		+	- 445:445
		+	#udp is not mandatory
		+	restart: always
		+	volumes:
		+	#watch out for semi-colons here between. must be colons NOT semi
		+	- ./localdir/from/docker-compose/root/:/anydirectory/on/docker/container
		+	environment:
		+	#these are semi-colons in the user section
		+	USER: username1;somepassword
		+	USER2: username2;somepassword
		+	USER3: username3;somepassword
		+	#I put these users on my host machine. disable ssh for them. i didn't bother with uid, gid.
		+	SHARE: SambaShareName;/location/on/docker/container;yes;no;no;username1,username2,username3
		+	SHARE2: SambaShareName2;/location/on/docker/container2;yes;no;no;username1,username2,username3
		+	#Be careful to avoid doing multiple Share of the same #. It's easy to overlook these.
		+	#e.g. with two SHARE2 items, only the second will be active
		+	SHARE3: SambaShareName3;/location/on/docker/container3;yes;no;no;username1,username2,username3
		+	#watch out for folders being owned by root on docker container. Login to container and check share permissions
		+	TZ: EST5EDT
		+	#Permissions was not required. If you are to use it, you can just put it as below.
		+	#there is no need to pass a value to it.
		+	# PERMISSIONS:
		+	#for further troubleshooting, download the git repo, and grep through the code.
		+	#another note: I had no issues doing samba shares, that were subfolders of a parent share.
		+	</pre>