mastodon.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
Generic Mastodon server for anyone to use.

Server stats:

8.1K
active users

#containerapps

0 posts0 participants0 posts today

Reposting since I moved instances and it’s only a few weeks away:

I’ll be talking at this year’s #SQLSaturday in #BatonRouge about getting started with modern #CloudNative practices using #Azure #ContainerApps. This event is totally free and I think tickets that include lunch are still available. Come see me and/or the tons of other awesome speakers who will be discussing all aspects of the Software Development Lifecycle!

sqlsaturday.com/2023-07-29-sql

I have been looking for documentation on how to use init containers in but I have not found any. Init containers are useful for running tasks before the main application starts, such as setting up configuration files or running migrations. However, it seems that Container Apps does not support this feature yet, or at least does not provide any guidance on implementing it. This is a bit frustrating. (cc: @anthonychu )

Replied to Anthony Chu

@anthonychu
I suggest
* to have a default of 8080 in all templates and guidances (this is already planned for the next version to the best of my knowledge). Also, the default examples of containers should be non-root. Right now it is the exact opposite.
* to have a clear warning of the binding issue in the system logs
* To work with desktop guys and to provide guidance on how to recreate the behaviour locally, to simplify developer flow.

Using privileged ports (<1024) in non-root containers can be pretty tricky. These ports require root access to bind to them, which may work on docker desktop, but not on cloud hosted environments like . I wish Docker Desktop could warn the developers about this issue when they try to use these ports. Maybe there is already a warning that I missed?