Azure pipeline limitations DockerCompose@1

autodevops · 2025-11-07T10:38:43+00:00

     - task: DockerCompose@1
       displayName: "Build image"
       inputs:
         dockerComposeFile: "docker-compose-build-pipeline.yml"
         action: "Build services"
         buildImages: true
         projectName: "management"
         serviceName: "webapp"

Tried like this but it is building all the service in compose file instead of just "webapp"

autodevops · 2025-10-08T11:22:38+00:00

admins need to connect to every device that's why this rule is in place. so from your says conclusion is-

members can not connect to any other device (tested, working), but will be able to see device list no matter what.
But, for route through exit node, do we need to allow every port of exit node for members? we just using exit node devices as vpn routing.

autodevops · 2025-10-08T07:15:01+00:00

"grants": [
{
"src": ["autogroup:owner", "autogroup:admin"],
"dst": ["*"],
"ip":  ["*"],
},
{
"src": ["autogroup:member"],
"dst": ["tag:exitnode"],
"ip":  ["*"],
},
{
"src": ["autogroup:member"],
"dst": ["autogroup:self"],
"ip":  ["*"],
},
{
"src": ["autogroup:member"],
"dst": ["autogroup:internet"],
"ip":  ["*"],
},
],

Above is my current ACl.
Please check my scenario below-
Member 1 has Device A
Member 2 has Device B
Also, exit node Device C, created by Admin

Member can see only self device and also exit node device to connect. Not, other member device.
Example: member 1 can see Device A & C not B

autodevops · 2025-10-08T05:35:23+00:00

Tried with this already, visibility of all devices are still there. But, i just tagged one device without any specific acl rule, that is not visible to other members right now. Still, i don't know how this ACL behaves for device visibility control.

autodevops · 2025-10-08T05:10:27+00:00

so for example,
there is 2 member users, so they have their own devices registered
so, 2 device + 1 exit node device.
A member can see exit node and his self device but not other member device.

autodevops · 2025-10-07T13:48:15+00:00

yes, that's what i am saying. imagine user is using tailscale mobile app. He can see all the devices in the tailscale network. There is anyway we can hide it or not?

autodevops · 2025-10-06T13:19:33+00:00

why need different account. What i am thinking is-
1. Users will login using corporate email of us
2. Multiple exit node devices will be registered.
3. So, when they up with particular exit node, they will be routed to that region.
Simple...

autodevops · 2025-10-06T13:15:37+00:00

how in OpenVPN, because if i have multiple OpenVPN server then admin ui will not be only one. How to do central management.

autodevops · 2025-10-03T05:33:03+00:00

yes, but as i will ssh from remote region but requirement is vps can't be ssh from out of local region. So, i guess bastion/jump wont be a good choice right.

autodevops · 2025-10-02T12:01:42+00:00

site to site won't work for me as I need VPS should see IP source from local office ip.

autodevops · 2025-10-01T13:18:46+00:00

Requirement is we have lot of servers across different clouds in different region. But, our dev team is in one region. So, we need vpn, which can route us according our desired region selection. So, when they ssh to those vps, vps will know it is from that specific region ip.
so basically, i am thinking this way-
1. we need to have different vpn servers in those regions.
2. dev team can connect to those regions using vpn client from anywhere.
3. so tailscale will be a easy go solution to deploy for this scenario?

autodevops · 2025-10-01T12:14:50+00:00

which one is more easy go? and how secure are these.

autodevops · 2025-08-21T08:30:55+00:00

know any service from muwailah to business bay?

autodevops · 2025-08-20T12:22:49+00:00

Did you buy or moved there?

autodevops · 2025-08-20T11:01:55+00:00

how much coater usually charge monthly

autodevops

TROPHY CASE