Closed Telokis closed 1 month ago
/attempt #3041
with your implementation plan/claim #3041
in the PR body to claim the bountyThank you for contributing to coollabsio/coolify!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🟢 @LEstradioto | Aug 14, 2024, 12:08:54 PM | #3068 |
/attempt #3041
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@LEstradioto | 2 bounties from 2 projects | Cancel attempt |
@Telokis After #3058 is merged, please reward the bounty! @LEstradioto Thanks for the PR!
@LEstradioto: You've been awarded a $10 bounty by Telokis0! 👉 Complete your Algora onboarding to collect the bounty.
Description
It's already happened 4 times that, when creating my resource, I select my own network but when checking "Connect To Predefined Network", the network the container is attached to is
coolify
.The first time I thought I simply selected the wrong network without paying attention but since then it's happened multiple times more.
Minimal Reproduction (if possible, example repository)
Projects
Production
Add new resource
Docker Compose
coolify
. (web
, in my case)docker-compose.yml
:Connect To Predefined Network
<-- Very important, we want to connect to theweb
networkDeploy
to create your containerssh
to connect to the server on which you deployed the servicedocker ps -a
grep glances` to find the container we just createddocker inspect glances-<uid>
to check the details of the container"Networks"
section, notice that the container is connected to thecoolify
network and not toweb
as configured.Exception or Error
No response
Version
v4.0.0-beta.319
Cloud?